Beam failure recovery

ABSTRACT

Systems, apparatuses, and methods are described for wireless communications. A wireless device may inform a base station of a failure of a beam failure recovery procedure for a secondary cell. The wireless device may include an indicator of the failure in a report providing, or configured to provide, values for signal strength or other characteristic of a downlink signal. The indicator may be in addition to, and/or may replace, one or more indicators of signal strength or other characteristic.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 16/372,858 (now U.S. Pat. No. 11,039,350), filed on Apr. 2, 2019, which claims the benefit of U.S. Provisional Application No. 62/651,419, filed on Apr. 2, 2018. The above-referenced applications are hereby incorporated by reference in their entirety.

BACKGROUND

A wireless device may be configured to receive transmissions via one of multiple different beams associated with a cell. Although this capability can increase cell capacity, individual beams may be subject to failure based on interruption (e.g., by passing vehicles or other objects), interference, transmission irregularities at a cell, etc. If a beam fails, action may be taken to recover the beam.

SUMMARY

The following summary presents a simplified summary of certain features. The summary is not an extensive overview and is not intended to identify key or critical elements.

Systems, apparatuses, and methods are described for reporting a beam failure recovery (BFR) procedure for a secondary cell. The BFR procedure may have been unsuccessful and/or may have otherwise failed. A wireless device may be unable to inform a base station of the BFR procedure for a secondary cell using the same procedure used for a primary cell. A wireless device may be configured to provide beam reporting for a secondary cell. That reporting, which may be sent via a physical uplink control channel (PUCCH) of the secondary cell and/or via a PUCCH of another cell, may include fields for indications of signal strength and/or one or more other characteristics of downlink signals received by the wireless device. The reporting may be modified to include an indication of a BFR procedure on the secondary cell. That indication of the BFR procedure may replace, in one or more of the fields, the indication of signal strength or other characteristic. The indication of the BFR procedure may be included in addition to indications of signal strength and/or other characteristics.

These and other features and advantages are described in greater detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in the accompanying drawings.

In the drawings, like numerals reference similar elements.

FIG. 1 shows an example radio access network (RAN) architecture.

FIG. 2A shows an example user plane protocol stack.

FIG. 2B shows an example control plane protocol stack.

FIG. 3 shows an example wireless device and two base stations.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink and downlink signal transmission.

FIG. 5A shows an example uplink channel mapping and example uplink physical signals.

FIG. 5B shows an example downlink channel mapping and example downlink physical signals.

FIG. 6 shows an example transmission time and/or reception time for a carrier.

FIG. 7A and FIG. 7B show example sets of orthogonal frequency division multiplexing (OFDM) subcarriers.

FIG. 8 shows example OFDM radio resources.

FIG. 9A shows an example channel state information reference signal (CSI-RS) and/or synchronization signal (SS) block transmission in a multi-beam system.

FIG. 9B shows an example downlink beam management procedure.

FIG. 10 shows an example of configured bandwidth parts (BWPs).

FIG. 11A and FIG. 11B show examples of multi connectivity.

FIG. 12 shows an example of a random access procedure.

FIG. 13 shows example medium access control (MAC) entities.

FIG. 14 shows an example RAN architecture.

FIG. 15 shows example radio resource control (RRC) states.

FIG. 16A, FIG. 16B and FIG. 16C show examples of a MAC subheader.

FIG. 17A and FIG. 17B show examples of uplink/downlink (UL/DL) MAC protocol data unit (PDU).

FIG. 18A and FIG. 18B show examples of logical channel identifiers (LCIDs).

FIG. 19A and FIG. 19B show examples of secondary cell activation and/or deactivation MAC control element (CE).

FIG. 20A and FIG. 20B show examples of a downlink beam failure.

FIG. 21 shows an example downlink beam failure recovery procedure.

FIG. 22 shows an example timeline for an example downlink beam failure recovery procedure.

FIG. 23 shows an example downlink beam failure recovery procedure.

FIG. 24 is another example timeline for an example downlink beam failure recovery procedure.

FIG. 25 shows a table of an example mapping of L1-RSRP values to 7-bit values.

FIG. 26A, FIG. 26B, FIG. 26C, and FIG. 26D show examples of reporting.

FIG. 27 shows example elements of a computing device that may be used to implement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings and descriptions provide examples. It is to be understood that the examples shown in the drawings and/or described are non-exclusive and that there are other examples of how features shown and described may be practiced.

Examples are provided for operation of wireless communication systems which may be used in the technical field of multicarrier communication systems. More particularly, the technology described herein may, for example, relate to failure recovery procedures and/or operations associated with failure recovery procedures.

The following acronyms are used throughout the drawings and/or descriptions, and are provided below for convenience although other acronyms may be introduced in the detailed description:

-   -   3GPP 3rd Generation Partnership Project     -   5GC 5G Core Network     -   ACK Acknowledgement     -   AMF Access and Mobility Management Function     -   ARQ Automatic Repeat Request     -   AS Access Stratum     -   ASIC Application-Specific Integrated Circuit     -   BA Bandwidth Adaptation     -   BCCH Broadcast Control Channel     -   BCH Broadcast Channel     -   BPSK Binary Phase Shift Keying     -   BWP Bandwidth Part     -   CA Carrier Aggregation     -   CC Component Carrier     -   CCCH Common Control CHannel     -   CDMA Code Division Multiple Access     -   CN Core Network     -   CP Cyclic Prefix     -   CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex     -   C-RNTI Cell-Radio Network Temporary Identifier     -   CS Configured Scheduling     -   CSI Channel State Information     -   CSI-RS Channel State Information-Reference Signal     -   CQI Channel Quality Indicator     -   CSS Common Search Space     -   CU Central Unit     -   DC Dual Connectivity     -   DCCH Dedicated Control Channel     -   DCI Downlink Control Information     -   DL Downlink     -   DL-SCH Downlink Shared CHannel     -   DM-RS DeModulation Reference Signal     -   DRB Data Radio Bearer     -   DRX Discontinuous Reception     -   DTCH Dedicated Traffic Channel     -   DU Distributed Unit     -   EPC Evolved Packet Core     -   E-UTRA Evolved UMTS Terrestrial Radio Access     -   E-UTRAN Evolved-Universal Terrestrial Radio Access Network     -   FDD Frequency Division Duplex     -   FPGA Field Programmable Gate Arrays     -   F1-C F1-Control plane     -   F1-U F1-User plane     -   gNB next generation Node B     -   HARQ Hybrid Automatic Repeat reQuest     -   HDL Hardware Description Languages     -   IE Information Element     -   IP Internet Protocol     -   LCID Logical Channel Identifier     -   LTE Long Term Evolution     -   MAC Media Access Control     -   MCG Master Cell Group     -   MCS Modulation and Coding Scheme     -   MeNB Master evolved Node B     -   MIB Master Information Block     -   MME Mobility Management Entity     -   MN Master Node     -   NACK Negative Acknowledgement     -   NAS Non-Access Stratum     -   NG CP Next Generation Control Plane     -   NGC Next Generation Core     -   NG-C NG-Control plane     -   ng-eNB next generation evolved Node B     -   NG-U NG-User plane     -   NR New Radio     -   NR MAC New Radio MAC     -   NR PDCP New Radio PDCP     -   NR PHY New Radio PHYsical     -   NR RLC New Radio RLC     -   NR RRC New Radio RRC     -   NSSAI Network Slice Selection Assistance Information     -   O&M Operation and Maintenance     -   OFDM Orthogonal Frequency Division Multiplexing     -   PBCH Physical Broadcast CHannel     -   PCC Primary Component Carrier     -   PCCH Paging Control CHannel     -   PCell Primary Cell     -   PCH Paging CHannel     -   PDCCH Physical Downlink Control CHannel     -   PDCP Packet Data Convergence Protocol     -   PDSCH Physical Downlink Shared CHannel     -   PDU Protocol Data Unit     -   PHICH Physical HARQ Indicator CHannel     -   PHY PHYsical     -   PLMN Public Land Mobile Network     -   PMI Precoding Matrix Indicator     -   PRACH Physical Random Access CHannel     -   PRB Physical Resource Block     -   PSCell Primary Secondary Cell     -   PSS Primary Synchronization Signal     -   pTAG primary Timing Advance Group     -   PT-RS Phase Tracking Reference Signal     -   PUCCH Physical Uplink Control CHannel     -   PUSCH Physical Uplink Shared CHannel     -   QAM Quadrature Amplitude Modulation     -   QFI Quality of Service Indicator     -   QoS Quality of Service     -   QPSK Quadrature Phase Shift Keying     -   RA Random Access     -   RACH Random Access CHannel     -   RAN Radio Access Network     -   RAT Radio Access Technology     -   RA-RNTI Random Access-Radio Network Temporary Identifier     -   RB Resource Blocks     -   RBG Resource Block Groups     -   RI Rank indicator     -   RLC Radio Link Control     -   RRC Radio Resource Control     -   RS Reference Signal     -   RSRP Reference Signal Received Power     -   SCC Secondary Component Carrier     -   SCell Secondary Cell     -   SCG Secondary Cell Group     -   SC-FDMA Single Carrier-Frequency Division Multiple Access     -   SDAP Service Data Adaptation Protocol     -   SDU Service Data Unit     -   SeNB Secondary evolved Node B     -   SFN System Frame Number     -   S-GW Serving GateWay     -   SI System Information     -   SIB System Information Block     -   SMF Session Management Function     -   SN Secondary Node     -   SpCell Special Cell     -   SRB Signaling Radio Bearer     -   SRS Sounding Reference Signal     -   SS Synchronization Signal     -   SSS Secondary Synchronization Signal     -   sTAG secondary Timing Advance Group     -   TA Timing Advance     -   TAG Timing Advance Group     -   TAI Tracking Area Identifier     -   TAT Time Alignment Timer     -   TB Transport Block     -   TC-RNTI Temporary Cell-Radio Network Temporary Identifier     -   TDD Time Division Duplex     -   TDMA Time Division Multiple Access     -   TTI Transmission Time Interval     -   UCI Uplink Control Information     -   UE User Equipment     -   UL Uplink     -   UL-SCH Uplink Shared CHannel     -   UPF User Plane Function     -   UPGW User Plane Gateway     -   VHDL VHSIC Hardware Description Language     -   Xn-C Xn-Control plane     -   Xn-U Xn-User plane

Examples described herein may be implemented using various physical layer modulation and transmission mechanisms. Example transmission mechanisms may include, but are not limited to: Code Division Multiple Access (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Time Division Multiple Access (TDMA), Wavelet technologies, and/or the like. Hybrid transmission mechanisms such as TDMA/CDMA, and/or OFDM/CDMA may be used. Various modulation schemes may be used for signal transmission in the physical layer. Examples of modulation schemes include, but are not limited to: phase, amplitude, code, a combination of these, and/or the like. An example radio transmission method may implement Quadrature Amplitude Modulation (QAM) using Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radio transmission may be enhanced by dynamically or semi-dynamically changing the modulation and coding scheme, for example, depending on transmission requirements and/or radio conditions.

FIG. 1 shows an example Radio Access Network (RAN) architecture. A RAN node may comprise a next generation Node B (gNB) (e.g., 120A, 120B) providing New Radio (NR) user plane and control plane protocol terminations towards a first wireless device (e.g., 110A). A RAN node may comprise a base station such as a next generation evolved Node B (ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards a second wireless device (e.g., 110B). A first wireless device 110A may communicate with a base station, such as a gNB 120A, over a Uu interface. A second wireless device 110B may communicate with a base station, such as an ng-eNB 120D, over a Uu interface.

A base station, such as a gNB (e.g., 120A, 120B, etc.) and/or an ng-eNB (e.g., 120C, 120D, etc.) may host functions such as radio resource management and scheduling, IP header compression, encryption and integrity protection of data, selection of Access and Mobility Management Function (AMF) at wireless device (e.g., User Equipment (UE)) attachment, routing of user plane and control plane data, connection setup and release, scheduling and transmission of paging messages (e.g., originated from the AMF), scheduling and transmission of system broadcast information (e.g., originated from the AMF or Operation and Maintenance (O&M)), measurement and measurement reporting configuration, transport level packet marking in the uplink, session management, support of network slicing, Quality of Service (QoS) flow management and mapping to data radio bearers, support of wireless devices in an inactive state (e.g., RRC_INACTIVE state), distribution function for Non-Access Stratum (NAS) messages, RAN sharing, dual connectivity, and/or tight interworking between NR and E-UTRA.

One or more first base stations (e.g., gNBs 120A and 120B) and/or one or more second base stations (e.g., ng-eNBs 120C and 120D) may be interconnected with each other via Xn interface. A first base station (e.g., gNB 120A, 120B, etc.) or a second base station (e.g., ng-eNB 120C, 120D, etc.) may be connected via NG interfaces to a network, such as a 5G Core Network (5GC). A 5GC may comprise one or more AMF/User Plan Function (UPF) functions (e.g., 130A and/or 130B). A base station (e.g., a gNB and/or an ng-eNB) may be connected to a UPF via an NG-User plane (NG-U) interface. The NG-U interface may provide delivery (e.g., non-guaranteed delivery) of user plane Protocol Data Units (PDUs) between a RAN node and the UPF. A base station (e.g., a gNB and/or an ng-eNB) may be connected to an AMF via an NG-Control plane (NG-C) interface. The NG-C interface may provide functions such as NG interface management, wireless device (e.g., UE) context management, wireless device (e.g., UE) mobility management, transport of NAS messages, paging, PDU session management, configuration transfer, and/or warning message transmission.

A UPF may host functions such as anchor point for intra-/inter-Radio Access Technology (RAT) mobility (e.g., if applicable), external PDU session point of interconnect to data network, packet routing and forwarding, packet inspection and user plane part of policy rule enforcement, traffic usage reporting, uplink classifier to support routing traffic flows to a data network, branching point to support multi-homed PDU session, quality of service (QoS) handling for user plane, packet filtering, gating, Uplink (UL)/Downlink (DL) rate enforcement, uplink traffic verification (e.g., Service Data Flow (SDF) to QoS flow mapping), downlink packet buffering, and/or downlink data notification triggering.

An AMF may host functions such as NAS signaling termination, NAS signaling security, Access Stratum (AS) security control, inter Core Network (CN) node signaling (e.g., for mobility between 3rd Generation Partnership Project (3GPP) access networks), idle mode wireless device reachability (e.g., control and execution of paging retransmission), registration area management, support of intra-system and inter-system mobility, access authentication, access authorization including check of roaming rights, mobility management control (e.g., subscription and/or policies), support of network slicing, and/or Session Management Function (SMF) selection.

FIG. 2A shows an example user plane protocol stack. A Service Data Adaptation Protocol (SDAP) (e.g., 211 and 221), Packet Data Convergence Protocol (PDCP) (e.g., 212 and 222), Radio Link Control (RLC) (e.g., 213 and 223), and Media Access Control (MAC) (e.g., 214 and 224) sublayers, and a Physical (PHY) (e.g., 215 and 225) layer, may be terminated in a wireless device (e.g., 110) and in a base station (e.g., 120) on a network side. A PHY layer may provide transport services to higher layers (e.g., MAC, RRC, etc.). Services and/or functions of a MAC sublayer may comprise mapping between logical channels and transport channels, multiplexing and/or demultiplexing of MAC Service Data Units (SDUs) belonging to the same or different logical channels into and/or from Transport Blocks (TBs) delivered to and/or from the PHY layer, scheduling information reporting, error correction through Hybrid Automatic Repeat request (HARQ) (e.g., one HARQ entity per carrier for Carrier Aggregation (CA)), priority handling between wireless devices such as by using dynamic scheduling, priority handling between logical channels of a wireless device such as by using logical channel prioritization, and/or padding. A MAC entity may support one or multiple numerologies and/or transmission timings. Mapping restrictions in a logical channel prioritization may control which numerology and/or transmission timing a logical channel may use. An RLC sublayer may support transparent mode (TM), unacknowledged mode (UM), and/or acknowledged mode (AM) transmission modes. The RLC configuration may be per logical channel with no dependency on numerologies and/or Transmission Time Interval (TTI) durations. Automatic Repeat Request (ARQ) may operate on any of the numerologies and/or TTI durations with which the logical channel is configured. Services and functions of the PDCP layer for the user plane may comprise, for example, sequence numbering, header compression and decompression, transfer of user data, reordering and duplicate detection, PDCP PDU routing (e.g., such as for split bearers), retransmission of PDCP SDUs, ciphering, deciphering and integrity protection, PDCP SDU discard, PDCP re-establishment and data recovery for RLC AM, and/or duplication of PDCP PDUs. Services and/or functions of SDAP may comprise, for example, mapping between a QoS flow and a data radio bearer. Services and/or functions of SDAP may comprise mapping a Quality of Service Indicator (QFI) in DL and UL packets. A protocol entity of SDAP may be configured for an individual PDU session.

FIG. 2B shows an example control plane protocol stack. A PDCP (e.g., 233 and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244) sublayers, and a PHY (e.g., 236 and 245) layer, may be terminated in a wireless device (e.g., 110), and in a base station (e.g., 120) on a network side, and perform service and/or functions described above. RRC (e.g., 232 and 241) may be terminated in a wireless device and a base station on a network side. Services and/or functions of RRC may comprise broadcast of system information related to AS and/or NAS; paging (e.g., initiated by a 5GC or a RAN); establishment, maintenance, and/or release of an RRC connection between the wireless device and RAN; security functions such as key management, establishment, configuration, maintenance, and/or release of Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs); mobility functions; QoS management functions; wireless device measurement reporting and control of the reporting; detection of and recovery from radio link failure; and/or NAS message transfer to/from NAS from/to a wireless device. NAS control protocol (e.g., 231 and 251) may be terminated in the wireless device and AMF (e.g., 130) on a network side. NAS control protocol may perform functions such as authentication, mobility management between a wireless device and an AMF (e.g., for 3GPP access and non-3GPP access), and/or session management between a wireless device and an SMF (e.g., for 3GPP access and non-3GPP access).

A base station may configure a plurality of logical channels for a wireless device. A logical channel of the plurality of logical channels may correspond to a radio bearer. The radio bearer may be associated with a QoS requirement. A base station may configure a logical channel to be mapped to one or more TTIs and/or numerologies in a plurality of TTIs and/or numerologies. The wireless device may receive Downlink Control Information (DCI) via a Physical Downlink Control CHannel (PDCCH) indicating an uplink grant. The uplink grant may be for a first TTI and/or a first numerology and may indicate uplink resources for transmission of a transport block. The base station may configure each logical channel in the plurality of logical channels with one or more parameters to be used by a logical channel prioritization procedure at the MAC layer of the wireless device. The one or more parameters may comprise, for example, priority, prioritized bit rate, etc. A logical channel in the plurality of logical channels may correspond to one or more buffers comprising data associated with the logical channel. The logical channel prioritization procedure may allocate the uplink resources to one or more first logical channels in the plurality of logical channels and/or to one or more MAC Control Elements (CEs). The one or more first logical channels may be mapped to the first TTI and/or the first numerology. The MAC layer at the wireless device may multiplex one or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel) in a MAC PDU (e.g., transport block). The MAC PDU may comprise a MAC header comprising a plurality of MAC sub-headers. A MAC sub-header in the plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD (e.g., logical channel) in the one or more MAC CEs and/or in the one or more MAC SDUs. A MAC CE and/or a logical channel may be configured with a Logical Channel IDentifier (LCID). An LCID for a logical channel and/or a MAC CE may be fixed and/or pre-configured. An LCID for a logical channel and/or MAC CE may be configured for the wireless device by the base station. The MAC sub-header corresponding to a MAC CE and/or a MAC SDU may comprise an LCID associated with the MAC CE and/or the MAC SDU.

A base station may activate, deactivate, and/or impact one or more processes (e.g., set values of one or more parameters of the one or more processes or start and/or stop one or more timers of the one or more processes) at the wireless device, for example, by using one or more MAC commands. The one or more MAC commands may comprise one or more MAC control elements. The one or more processes may comprise activation and/or deactivation of PDCP packet duplication for one or more radio bearers. The base station may send (e.g., transmit) a MAC CE comprising one or more fields. The values of the fields may indicate activation and/or deactivation of PDCP duplication for the one or more radio bearers. The one or more processes may comprise Channel State Information (CSI) transmission for one or more cells. The base station may send (e.g., transmit) one or more MAC CEs indicating activation and/or deactivation of the CSI transmission on the one or more cells. The one or more processes may comprise activation and/or deactivation of one or more secondary cells. The base station may send (e.g., transmit) a MA CE indicating activation and/or deactivation of one or more secondary cells. The base station may send (e.g., transmit) one or more MAC CEs indicating starting and/or stopping of one or more Discontinuous Reception (DRX) timers at the wireless device. The base station may send (e.g., transmit) one or more MAC CEs indicating one or more timing advance values for one or more Timing Advance Groups (TAGs).

FIG. 3 shows an example of base stations (base station 1, 120A, and base station 2, 120B) and a wireless device 110. The wireless device 110 may comprise a UE or any other wireless device. The base station (e.g., 120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, or any other base station. A wireless device and/or a base station may perform one or more functions of a relay node. The base station 1, 120A, may comprise at least one communication interface 320A (e.g., a wireless modem, an antenna, a wired modem, and/or the like), at least one processor 321A, and at least one set of program code instructions 323A that may be stored in non-transitory memory 322A and executable by the at least one processor 321A. The base station 2, 120B, may comprise at least one communication interface 320B, at least one processor 321B, and at least one set of program code instructions 323B that may be stored in non-transitory memory 322B and executable by the at least one processor 321B.

A base station may comprise any number of sectors, for example: 1, 2, 3, 4, or 6 sectors. A base station may comprise any number of cells, for example, ranging from 1 to 50 cells or more. A cell may be categorized, for example, as a primary cell or secondary cell. At Radio Resource Control (RRC) connection establishment, re-establishment, handover, etc., a serving cell may provide NAS (non-access stratum) mobility information (e.g., Tracking Area Identifier (TAI)). At RRC connection re-establishment and/or handover, a serving cell may provide security input. This serving cell may be referred to as the Primary Cell (PCell). In the downlink, a carrier corresponding to the PCell may be a DL Primary Component Carrier (PCC). In the uplink, a carrier may be an UL PCC. Secondary Cells (SCells) may be configured to form together with a PCell a set of serving cells, for example, depending on wireless device capabilities. In a downlink, a carrier corresponding to an SCell may be a downlink secondary component carrier (DL SCC). In an uplink, a carrier may be an uplink secondary component carrier (UL SCC). An SCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned a physical cell ID and/or a cell index. A carrier (downlink and/or uplink) may belong to one cell. The cell ID and/or cell index may identify the downlink carrier and/or uplink carrier of the cell (e.g., depending on the context it is used). A cell ID may be equally referred to as a carrier ID, and a cell index may be referred to as a carrier index. A physical cell ID and/or a cell index may be assigned to a cell. A cell ID may be determined using a synchronization signal transmitted via a downlink carrier. A cell index may be determined using RRC messages. A first physical cell ID for a first downlink carrier may indicate that the first physical cell ID is for a cell comprising the first downlink carrier. The same concept may be used, for example, with carrier activation and/or deactivation (e.g., secondary cell activation and/or deactivation). A first carrier that is activated may indicate that a cell comprising the first carrier is activated.

A base station may send (e.g., transmit) to a wireless device one or more messages (e.g., RRC messages) comprising a plurality of configuration parameters for one or more cells. One or more cells may comprise at least one primary cell and at least one secondary cell. An RRC message may be broadcasted and/or unicasted to the wireless device. Configuration parameters may comprise common parameters and dedicated parameters.

Services and/or functions of an RRC sublayer may comprise at least one of: broadcast of system information related to AS and/or NAS; paging initiated by a 5GC and/or an NG-RAN; establishment, maintenance, and/or release of an RRC connection between a wireless device and an NG-RAN, which may comprise at least one of addition, modification, and/or release of carrier aggregation; and/or addition, modification, and/or release of dual connectivity in NR or between E-UTRA and NR. Services and/or functions of an RRC sublayer may comprise at least one of security functions comprising key management; establishment, configuration, maintenance, and/or release of Signaling Radio Bearers (SRBs) and/or Data Radio Bearers (DRBs); mobility functions which may comprise at least one of a handover (e.g., intra NR mobility or inter-RAT mobility) and/or a context transfer; and/or a wireless device cell selection and/or reselection and/or control of cell selection and reselection. Services and/or functions of an RRC sublayer may comprise at least one of QoS management functions; a wireless device measurement configuration/reporting; detection of and/or recovery from radio link failure; and/or NAS message transfer to and/or from a core network entity (e.g., AMF, Mobility Management Entity (MME)) from and/or to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state, and/or an RRC_Connected state for a wireless device. In an RRC_Idle state, a wireless device may perform at least one of: Public Land Mobile Network (PLMN) selection; receiving broadcasted system information; cell selection and/or re-selection; monitoring and/or receiving a paging for mobile terminated data initiated by 5GC; paging for mobile terminated data area managed by 5GC; and/or DRX for CN paging configured via NAS. In an RRC_Inactive state, a wireless device may perform at least one of: receiving broadcasted system information; cell selection and/or re-selection; monitoring and/or receiving a RAN and/or CN paging initiated by an NG-RAN and/or a 5GC; RAN-based notification area (RNA) managed by an NG-RAN; and/or DRX for a RAN and/or CN paging configured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station (e.g., NG-RAN) may keep a 5GC-NG-RAN connection (e.g., both C/U-planes) for the wireless device; and/or store a wireless device AS context for the wireless device. In an RRC_Connected state of a wireless device, a base station (e.g., NG-RAN) may perform at least one of: establishment of 5GC-NG-RAN connection (both C/U-planes) for the wireless device; storing a UE AS context for the wireless device; send (e.g., transmit) and/or receive of unicast data to and/or from the wireless device; and/or network-controlled mobility based on measurement results received from the wireless device. In an RRC_Connected state of a wireless device, an NG-RAN may know a cell to which the wireless device belongs.

System information (SI) may be divided into minimum SI and other SI. The minimum SI may be periodically broadcast. The minimum SI may comprise basic information required for initial access and/or information for acquiring any other SI broadcast periodically and/or provisioned on-demand (e.g., scheduling information). The other SI may either be broadcast, and/or be provisioned in a dedicated manner, such as either triggered by a network and/or upon request from a wireless device. A minimum SI may be transmitted via two different downlink channels using different messages (e.g., MasterInformationBlock and SystemInformationBlockType1). Another SI may be transmitted via SystemInformationBlockType2. For a wireless device in an RRC_Connected state, dedicated RRC signaling may be used for the request and delivery of the other SI. For the wireless device in the RRC_Idle state and/or in the RRC_Inactive state, the request may trigger a random-access procedure.

A wireless device may report its radio access capability information, which may be static. A base station may request one or more indications of capabilities for a wireless device to report based on band information. A temporary capability restriction request may be sent by the wireless device (e.g., if allowed by a network) to signal the limited availability of some capabilities (e.g., due to hardware sharing, interference, and/or overheating) to the base station. The base station may confirm or reject the request. The temporary capability restriction may be transparent to 5GC (e.g., static capabilities may be stored in 5GC).

A wireless device may have an RRC connection with a network, for example, if CA is configured. At RRC connection establishment, re-establishment, and/or handover procedures, a serving cell may provide NAS mobility information. At RRC connection re-establishment and/or handover, a serving cell may provide a security input. This serving cell may be referred to as the PCell. SCells may be configured to form together with the PCell a set of serving cells, for example, depending on the capabilities of the wireless device. The configured set of serving cells for the wireless device may comprise a PCell and one or more SCells.

The reconfiguration, addition, and/or removal of SCells may be performed by RRC messaging. At intra-NR handover, RRC may add, remove, and/or reconfigure SCells for usage with the target PCell. Dedicated RRC signaling may be used (e.g., if adding a new SCell) to send all required system information of the SCell (e.g., if in connected mode, wireless devices may not acquire broadcasted system information directly from the SCells).

The purpose of an RRC connection reconfiguration procedure may be to modify an RRC connection, (e.g., to establish, modify, and/or release RBs; to perform handover; to setup, modify, and/or release measurements, for example, to add, modify, and/or release SCells and cell groups). NAS dedicated information may be transferred from the network to the wireless device, for example, as part of the RRC connection reconfiguration procedure. The RRCConnectionReconfiguration message may be a command to modify an RRC connection. One or more RRC messages may convey information for measurement configuration, mobility control, and/or radio resource configuration (e.g., RBs, MAC main configuration, and/or physical channel configuration), which may comprise any associated dedicated NAS information and/or security configuration. The wireless device may perform an SCell release, for example, if the received RRC Connection Reconfiguration message includes the sCellToReleaseList. The wireless device may perform SCell additions or modification, for example, if the received RRC Connection Reconfiguration message includes the sCellToAddModList.

An RRC connection establishment, reestablishment, and/or resume procedure may be to establish, reestablish, and/or resume an RRC connection, respectively. An RRC connection establishment procedure may comprise SRB1 establishment. The RRC connection establishment procedure may be used to transfer the initial NAS dedicated information and/or message from a wireless device to an E-UTRAN. The RRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be used to transfer measurement results from a wireless device to an NG-RAN. The wireless device may initiate a measurement report procedure, for example, after successful security activation. A measurement report message may be used to send (e.g., transmit) measurement results.

The wireless device 110 may comprise at least one communication interface 310 (e.g., a wireless modem, an antenna, and/or the like), at least one processor 314, and at least one set of program code instructions 316 that may be stored in non-transitory memory 315 and executable by the at least one processor 314. The wireless device 110 may further comprise at least one of at least one speaker and/or microphone 311, at least one keypad 312, at least one display and/or touchpad 313, at least one power source 317, at least one global positioning system (GPS) chipset 318, and/or other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of the base station 1 120A, and/or the processor 321B of the base station 2 120B may comprise at least one of a general-purpose processor, a digital signal processor (DSP), a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and/or other programmable logic device, discrete gate and/or transistor logic, discrete hardware components, and/or the like. The processor 314 of the wireless device 110, the processor 321A in base station 1 120A, and/or the processor 321B in base station 2 120B may perform at least one of signal coding and/or processing, data processing, power control, input/output processing, and/or any other functionality that may enable the wireless device 110, the base station 1 120A and/or the base station 2 120B to operate in a wireless environment.

The processor 314 of the wireless device 110 may be connected to and/or in communication with the speaker and/or microphone 311, the keypad 312, and/or the display and/or touchpad 313. The processor 314 may receive user input data from and/or provide user output data to the speaker and/or microphone 311, the keypad 312, and/or the display and/or touchpad 313. The processor 314 in the wireless device 110 may receive power from the power source 317 and/or may be configured to distribute the power to the other components in the wireless device 110. The power source 317 may comprise at least one of one or more dry cell batteries, solar cells, fuel cells, and/or the like. The processor 314 may be connected to the GPS chipset 318. The GPS chipset 318 may be configured to provide geographic location information of the wireless device 110.

The processor 314 of the wireless device 110 may further be connected to and/or in communication with other peripherals 319, which may comprise one or more software and/or hardware modules that may provide additional features and/or functionalities. For example, the peripherals 319 may comprise at least one of an accelerometer, a satellite transceiver, a digital camera, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, and/or the like.

The communication interface 320A of the base station 1, 120A, and/or the communication interface 320B of the base station 2, 120B, may be configured to communicate with the communication interface 310 of the wireless device 110, for example, via a wireless link 330A and/or via a wireless link 330B, respectively. The communication interface 320A of the base station 1, 120A, may communicate with the communication interface 320B of the base station 2 and/or other RAN and/or core network nodes.

The wireless link 330A and/or the wireless link 330B may comprise at least one of a bi-directional link and/or a directional link. The communication interface 310 of the wireless device 110 may be configured to communicate with the communication interface 320A of the base station 1 120A and/or with the communication interface 320B of the base station 2 120B. The base station 1 120A and the wireless device 110, and/or the base station 2 120B and the wireless device 110, may be configured to send and receive transport blocks, for example, via the wireless link 330A and/or via the wireless link 330B, respectively. The wireless link 330A and/or the wireless link 330B may use at least one frequency carrier. Transceiver(s) may be used. A transceiver may be a device that comprises both a transmitter and a receiver. Transceivers may be used in devices such as wireless devices, base stations, relay nodes, computing devices, and/or the like. Radio technology may be implemented in the communication interface 310, 320A, and/or 320B, and the wireless link 330A and/or 330B. The radio technology may comprise one or more elements shown in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6 , FIG. 7A, FIG. 7B, FIG. 8 , and associated text, described below.

Other nodes in a wireless network (e.g. AMF, UPF, SMF, etc.) may comprise one or more communication interfaces, one or more processors, and memory storing instructions. A node (e.g., wireless device, base station, AMF, SMF, UPF, servers, switches, antennas, and/or the like) may comprise one or more processors, and memory storing instructions that when executed by the one or more processors causes the node to perform certain processes and/or functions. Single-carrier and/or multi-carrier communication operation may be performed. A non-transitory tangible computer readable media may comprise instructions executable by one or more processors to cause operation of single-carrier and/or multi-carrier communications. An article of manufacture may comprise a non-transitory tangible computer readable machine-accessible medium having instructions encoded thereon for enabling programmable hardware to cause a node to enable operation of single-carrier and/or multi-carrier communications. The node may include processors, memory, interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, a firmware interface, a software interface, and/or a combination thereof. The hardware interface may comprise connectors, wires, and/or electronic devices such as drivers, amplifiers, and/or the like. The software interface may comprise code stored in a memory device to implement protocol(s), protocol layers, communication drivers, device drivers, combinations thereof, and/or the like. The firmware interface may comprise a combination of embedded hardware and/or code stored in (and/or in communication with) a memory device to implement connections, electronic device operations, protocol(s), protocol layers, communication drivers, device drivers, hardware operations, combinations thereof, and/or the like.

A communication network may comprise the wireless device 110, the base station 1, 120A, the base station 2, 120B, and/or any other device. The communication network may comprise any number and/or type of devices, such as, for example, computing devices, wireless devices, mobile devices, handsets, tablets, laptops, internet of things (IoT) devices, hotspots, cellular repeaters, computing devices, and/or, more generally, user equipment (e.g., UE). Although one or more of the above types of devices may be referenced herein (e.g., UE, wireless device, computing device, etc.), it should be understood that any device herein may comprise any one or more of the above types of devices or similar devices. The communication network, and any other network referenced herein, may comprise an LTE network, a 5G network, or any other network for wireless communications. Apparatuses, systems, and/or methods described herein may generally be described as implemented on one or more devices (e.g., wireless device, base station, eNB, gNB, computing device, etc.), in one or more networks, but it will be understood that one or more features and steps may be implemented on any device and/or in any network. As used throughout, the term “base station” may comprise one or more of: a base station, a node, a Node B, a gNB, an eNB, an ng-eNB, a relay node (e.g., an integrated access and backhaul (IAB) node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an access point (e.g., a WiFi access point), a computing device, a device capable of wirelessly communicating, or any other device capable of sending and/or receiving signals. As used throughout, the term “wireless device” may comprise one or more of: a UE, a handset, a mobile device, a computing device, a node, a device capable of wirelessly communicating, or any other device capable of sending and/or receiving signals. Any reference to one or more of these terms/devices also considers use of any other term/device mentioned above.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink and downlink signal transmission. FIG. 4A shows an example uplink transmitter for at least one physical channel. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may comprise at least one of: scrambling (e.g., by Scrambling); modulation of scrambled bits to generate complex-valued symbols (e.g., by a Modulation mapper); mapping of the complex-valued modulation symbols onto one or several transmission layers (e.g., by a Layer mapper); transform precoding to generate complex-valued symbols (e.g., by a Transform precoder); precoding of the complex-valued symbols (e.g., by a Precoder); mapping of precoded complex-valued symbols to resource elements (e.g., by a Resource element mapper); generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDM signal for an antenna port (e.g., by a signal gen.); and/or the like. A SC-FDMA signal for uplink transmission may be generated, for example, if transform precoding is enabled. A CP-OFDM signal for uplink transmission may be generated by FIG. 4A, for example, if transform precoding is not enabled. These functions are shown as examples and other mechanisms may be implemented.

FIG. 4B shows an example of modulation and up-conversion to the carrier frequency of a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and/or for the complex-valued Physical Random Access CHannel (PRACH) baseband signal. Filtering may be performed prior to transmission.

FIG. 4C shows an example of downlink transmissions. The baseband signal representing a downlink physical channel may perform one or more functions. The one or more functions may comprise: scrambling of coded bits in a codeword to be transmitted on a physical channel (e.g., by Scrambling); modulation of scrambled bits to generate complex-valued modulation symbols (e.g., by a Modulation mapper); mapping of the complex-valued modulation symbols onto one or several transmission layers (e.g., by a Layer mapper); precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports (e.g., by Precoding); mapping of complex-valued modulation symbols for an antenna port to resource elements (e.g., by a Resource element mapper); generation of complex-valued time-domain OFDM signal for an antenna port (e.g., by an OFDM signal gen.); and/or the like. These functions are shown as examples and other mechanisms may be implemented.

A base station may send (e.g., transmit) a first symbol and a second symbol on an antenna port, to a wireless device. The wireless device may infer the channel (e.g., fading gain, multipath delay, etc.) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port. A first antenna port and a second antenna port may be quasi co-located, for example, if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: delay spread; Doppler spread; Doppler shift; average gain; average delay; and/or spatial receiving (Rx) parameters.

FIG. 4D shows an example modulation and up-conversion to the carrier frequency of the complex-valued OFDM baseband signal for an antenna port. Filtering may be performed prior to transmission.

FIG. 5A shows example uplink channel mapping and example uplink physical signals. A physical layer may provide one or more information transfer services to a MAC and/or one or more higher layers. The physical layer may provide the one or more information transfer services to the MAC via one or more transport channels. An information transfer service may indicate how and/or with what characteristics data is transferred over the radio interface.

Uplink transport channels may comprise an Uplink-Shared CHannel (UL-SCH) 501 and/or a Random Access CHannel (RACH) 502. A wireless device may send (e.g., transmit) one or more uplink DM-RSs 506 to a base station for channel estimation, for example, for coherent demodulation of one or more uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). The wireless device may send (e.g., transmit) to a base station at least one uplink DM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at least one uplink DM-RS 506 may be spanning a same frequency range as a corresponding physical channel. The base station may configure the wireless device with one or more uplink DM-RS configurations. At least one DM-RS configuration may support a front-loaded DM-RS pattern. A front-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may be configured to send (e.g., transmit) at one or more symbols of a PUSCH and/or PUCCH. The base station may semi-statically configure the wireless device with a maximum number of front-loaded DM-RS symbols for PUSCH and/or PUCCH. The wireless device may schedule a single-symbol DM-RS and/or double symbol DM-RS based on a maximum number of front-loaded DM-RS symbols, wherein the base station may configure the wireless device with one or more additional uplink DM-RS for PUSCH and/or PUCCH. A new radio network may support, for example, at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RS location, DM-RS pattern, and/or scrambling sequence may be same or different.

Whether or not an uplink PT-RS 507 is present may depend on an RRC configuration. A presence of the uplink PT-RS may be wireless device-specifically configured. A presence and/or a pattern of the uplink PT-RS 507 in a scheduled resource may be wireless device-specifically configured by a combination of RRC signaling and/or association with one or more parameters used for other purposes (e.g., Modulation and Coding Scheme (MCS)) which may be indicated by DCI. If configured, a dynamic presence of uplink PT-RS 507 may be associated with one or more DCI parameters comprising at least a MCS. A radio network may support a plurality of uplink PT-RS densities defined in time/frequency domain. If present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. A wireless device may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be less than a number of DM-RS ports in a scheduled resource. The uplink PT-RS 507 may be confined in the scheduled time/frequency duration for a wireless device.

A wireless device may send (e.g., transmit) an SRS 508 to a base station for channel state estimation, for example, to support uplink channel dependent scheduling and/or link adaptation. The SRS 508 sent (e.g., transmitted) by the wireless device may allow for the base station to estimate an uplink channel state at one or more different frequencies. A base station scheduler may use an uplink channel state to assign one or more resource blocks of a certain quality (e.g., above a quality threshold) for an uplink PUSCH transmission from the wireless device. The base station may semi-statically configure the wireless device with one or more SRS resource sets. For an SRS resource set, the base station may configure the wireless device with one or more SRS resources. An SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter. An SRS resource in each of one or more SRS resource sets may be sent (e.g., transmitted) at a time instant, for example, if a higher layer parameter indicates beam management. The wireless device may send (e.g., transmit) one or more SRS resources in different SRS resource sets simultaneously. A new radio network may support aperiodic, periodic, and/or semi-persistent SRS transmissions. The wireless device may send (e.g., transmit) SRS resources, for example, based on one or more trigger types. The one or more trigger types may comprise higher layer signaling (e.g., RRC) and/or one or more DCI formats (e.g., at least one DCI format may be used for a wireless device to select at least one of one or more configured SRS resource sets). An SRS trigger type 0 may refer to an SRS triggered based on a higher layer signaling. An SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. The wireless device may be configured to send (e.g., transmit) the SRS 508 after a transmission of PUSCH 503 and corresponding uplink DM-RS 506, for example, if PUSCH 503 and the SRS 508 are transmitted in a same slot.

A base station may semi-statically configure a wireless device with one or more SRS configuration parameters indicating at least one of following: an SRS resource configuration identifier, a number of SRS ports, time domain behavior of SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS), slot (mini-slot, and/or subframe) level periodicity and/or offset for a periodic and/or aperiodic SRS resource, a number of OFDM symbols in a SRS resource, starting OFDM symbol of a SRS resource, an SRS bandwidth, a frequency hopping bandwidth, a cyclic shift, and/or an SRS sequence ID.

FIG. 5B shows an example downlink channel mapping and downlink physical signals. Downlink transport channels may comprise a Downlink-Shared CHannel (DL-SCH) 511, a Paging CHannel (PCH) 512, and/or a Broadcast CHannel (BCH) 513. A transport channel may be mapped to one or more corresponding physical channels. A UL-SCH 501 may be mapped to a Physical Uplink Shared CHannel (PUSCH) 503. A RACH 502 may be mapped to a PRACH 505. A DL-SCH 511 and a PCH 512 may be mapped to a Physical Downlink Shared CHannel (PDSCH) 514. A BCH 513 may be mapped to a Physical Broadcast CHannel (PBCH) 516.

A radio network may comprise one or more downlink and/or uplink transport channels. The radio network may comprise one or more physical channels without a corresponding transport channel. The one or more physical channels may be used for an Uplink Control Information (UCI) 509 and/or a Downlink Control Information (DCI) 517. A Physical Uplink Control CHannel (PUCCH) 504 may carry UCI 509 from a wireless device to a base station. A Physical Downlink Control CHannel (PDCCH) 515 may carry the DCI 517 from a base station to a wireless device. The radio network (e.g., NR) may support the UCI 509 multiplexing in the PUSCH 503, for example, if the UCI 509 and the PUSCH 503 transmissions may coincide in a slot (e.g., at least in part). The UCI 509 may comprise at least one of a CSI, an Acknowledgement (ACK)/Negative Acknowledgement (NACK), and/or a scheduling request. The DCI 517 via the PDCCH 515 may indicate at least one of following: one or more downlink assignments and/or one or more uplink scheduling grants.

In uplink, a wireless device may send (e.g., transmit) one or more Reference Signals (RSs) to a base station. The one or more RSs may comprise at least one of a Demodulation-RS (DM-RS) 506, a Phase Tracking-RS (PT-RS) 507, and/or a Sounding RS (SRS) 508. In downlink, a base station may send (e.g., transmit, unicast, multicast, and/or broadcast) one or more RSs to a wireless device. The one or more RSs may comprise at least one of a Primary Synchronization Signal (PSS)/Secondary Synchronization Signal (SSS) 521, a CSI-RS 522, a DM-RS 523, and/or a PT-RS 524.

In a time domain, an SS/PBCH block may comprise one or more OFDM symbols (e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) within the SS/PBCH block. An SS/PBCH block may comprise the PSS/SSS 521 and/or the PBCH 516. In the frequency domain, an SS/PBCH block may comprise one or more contiguous subcarriers (e.g., 240 contiguous subcarriers with the subcarriers numbered in increasing order from 0 to 239) within the SS/PBCH block. The PSS/SSS 521 may occupy, for example, 1 OFDM symbol and 127 subcarriers. The PBCH 516 may span across, for example, 3 OFDM symbols and 240 subcarriers. A wireless device may assume that one or more SS/PBCH blocks transmitted with a same block index may be quasi co-located, for example, with respect to Doppler spread, Doppler shift, average gain, average delay, and/or spatial Rx parameters. A wireless device may not assume quasi co-location for other SS/PBCH block transmissions. A periodicity of an SS/PBCH block may be configured by a radio network (e.g., by an RRC signaling). One or more time locations in which the SS/PBCH block may be sent may be determined by sub-carrier spacing. A wireless device may assume a band-specific sub-carrier spacing for an SS/PBCH block, for example, unless a radio network has configured the wireless device to assume a different sub-carrier spacing.

The downlink CSI-RS 522 may be used for a wireless device to acquire channel state information. A radio network may support periodic, aperiodic, and/or semi-persistent transmission of the downlink CSI-RS 522. A base station may semi-statically configure and/or reconfigure a wireless device with periodic transmission of the downlink CSI-RS 522. A configured CSI-RS resources may be activated and/or deactivated. For semi-persistent transmission, an activation and/or deactivation of a CSI-RS resource may be triggered dynamically. A CSI-RS configuration may comprise one or more parameters indicating at least a number of antenna ports. A base station may configure a wireless device with 32 ports, or any other number of ports. A base station may semi-statically configure a wireless device with one or more CSI-RS resource sets. One or more CSI-RS resources may be allocated from one or more CSI-RS resource sets to one or more wireless devices. A base station may semi-statically configure one or more parameters indicating CSI RS resource mapping, for example, time-domain location of one or more CSI-RS resources, a bandwidth of a CSI-RS resource, and/or a periodicity. A wireless device may be configured to use the same OFDM symbols for the downlink CSI-RS 522 and the Control Resource Set (CORESET), for example, if the downlink CSI-RS 522 and the CORESET are spatially quasi co-located and resource elements associated with the downlink CSI-RS 522 are the outside of PRBs configured for the CORESET. A wireless device may be configured to use the same OFDM symbols for downlink CSI-RS 522 and SSB/PBCH, for example, if the downlink CSI-RS 522 and SSB/PBCH are spatially quasi co-located and resource elements associated with the downlink CSI-RS 522 are outside of the PRBs configured for the SSB/PBCH.

A wireless device may send (e.g., transmit) one or more downlink DM-RSs 523 to a base station for channel estimation, for example, for coherent demodulation of one or more downlink physical channels (e.g., PDSCH 514). A radio network may support one or more variable and/or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a front-loaded DM-RS pattern. A front-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). A base station may semi-statically configure a wireless device with a maximum number of front-loaded DM-RS symbols for PDSCH 514. A DM-RS configuration may support one or more DM-RS ports. A DM-RS configuration may support at least 8 orthogonal downlink DM-RS ports, for example, for single user-MIMO. ADM-RS configuration may support 12 orthogonal downlink DM-RS ports, for example, for multiuser-MIMO. A radio network may support, for example, at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RS location, DM-RS pattern, and/or scrambling sequence may be the same or different.

Whether or not the downlink PT-RS 524 is present may depend on an RRC configuration. A presence of the downlink PT-RS 524 may be wireless device-specifically configured. A presence and/or a pattern of the downlink PT-RS 524 in a scheduled resource may be wireless device-specifically configured, for example, by a combination of RRC signaling and/or an association with one or more parameters used for other purposes (e.g., MCS) which may be indicated by the DCI. If configured, a dynamic presence of the downlink PT-RS 524 may be associated with one or more DCI parameters comprising at least MCS. A radio network may support a plurality of PT-RS densities in a time/frequency domain. If present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. A wireless device may assume the same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be less than a number of DM-RS ports in a scheduled resource. The downlink PT-RS 524 may be confined in the scheduled time/frequency duration for a wireless device.

FIG. 6 shows an example transmission time and reception time for a carrier. A multicarrier OFDM communication system may include one or more carriers, for example, ranging from 1 to 32 carriers (such as for carrier aggregation) or ranging from 1 to 64 carriers (such as for dual connectivity). Different radio frame structures may be supported (e.g., for FDD and/or for TDD duplex mechanisms). FIG. 6 shows an example frame timing. Downlink and uplink transmissions may be organized into radio frames 601. Radio frame duration may be 10 milliseconds (ms). A 10 ms radio frame 601 may be divided into ten equally sized subframes 602, each with a 1 ms duration. Subframe(s) may comprise one or more slots (e.g., slots 603 and 605) depending on subcarrier spacing and/or CP length. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz and 480 kHz subcarrier spacing may comprise one, two, four, eight, sixteen and thirty-two slots, respectively. In FIG. 6 , a subframe may be divided into two equally sized slots 603 with 0.5 ms duration. For example, 10 subframes may be available for downlink transmission and 10 subframes may be available for uplink transmissions in a 10 ms interval. Other subframe durations such as, for example, 0.5 ms, 1 ms, 2 ms, and 5 ms may be supported. Uplink and downlink transmissions may be separated in the frequency domain. Slot(s) may include a plurality of OFDM symbols 604. The number of OFDM symbols 604 in a slot 605 may depend on the cyclic prefix length. A slot may be 14 OFDM symbols for the same subcarrier spacing of up to 480 kHz with normal CP. A slot may be 12 OFDM symbols for the same subcarrier spacing of 60 kHz with extended CP. A slot may comprise downlink, uplink, and/or a downlink part and an uplink part, and/or alike.

FIG. 7A shows example sets of OFDM subcarriers. A base station may communicate with a wireless device using a carrier having an example channel bandwidth 700. Arrow(s) in the example may depict a subcarrier in a multicarrier OFDM system. The OFDM system may use technology such as OFDM technology, SC-FDMA technology, and/or the like. An arrow 701 shows a subcarrier transmitting information symbols. A subcarrier spacing 702, between two contiguous subcarriers in a carrier, may be any one of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, or any other frequency. Different subcarrier spacing may correspond to different transmission numerologies. A transmission numerology may comprise at least: a numerology index; a value of subcarrier spacing; and/or a type of cyclic prefix (CP). A base station may send (e.g., transmit) to and/or receive from a wireless device via a number of subcarriers 703 in a carrier. A bandwidth occupied by a number of subcarriers 703 (e.g., transmission bandwidth) may be smaller than the channel bandwidth 700 of a carrier, for example, due to guard bands 704 and 705. Guard bands 704 and 705 may be used to reduce interference to and from one or more neighbor carriers. A number of subcarriers (e.g., transmission bandwidth) in a carrier may depend on the channel bandwidth of the carrier and/or the subcarrier spacing. A transmission bandwidth, for a carrier with a 20 MHz channel bandwidth and a 15 kHz subcarrier spacing, may be in number of 1024 subcarriers.

A base station and a wireless device may communicate with multiple component carriers (CCs), for example, if configured with CA. Different component carriers may have different bandwidth and/or different subcarrier spacing, for example, if CA is supported. A base station may send (e.g., transmit) a first type of service to a wireless device via a first component carrier. The base station may send (e.g., transmit) a second type of service to the wireless device via a second component carrier. Different types of services may have different service requirements (e.g., data rate, latency, reliability), which may be suitable for transmission via different component carriers having different subcarrier spacing and/or different bandwidth.

FIG. 7B shows examples of component carriers. A first component carrier may comprise a first number of subcarriers 706 having a first subcarrier spacing 709. A second component carrier may comprise a second number of subcarriers 707 having a second subcarrier spacing 710. A third component carrier may comprise a third number of subcarriers 708 having a third subcarrier spacing 711. Carriers in a multicarrier OFDM communication system may be contiguous carriers, non-contiguous carriers, or a combination of both contiguous and non-contiguous carriers.

FIG. 8 shows an example of OFDM radio resources. A carrier may have a transmission bandwidth 801. A resource grid may be in a structure of frequency domain 802 and time domain 803. A resource grid may comprise a first number of OFDM symbols in a subframe and a second number of resource blocks, starting from a common resource block indicated by higher-layer signaling (e.g., RRC signaling), for a transmission numerology and a carrier. In a resource grid, a resource element 805 may comprise a resource unit that may be identified by a subcarrier index and a symbol index. A subframe may comprise a first number of OFDM symbols 807 that may depend on a numerology associated with a carrier. A subframe may have 14 OFDM symbols for a carrier, for example, if a subcarrier spacing of a numerology of a carrier is 15 kHz. A subframe may have 28 OFDM symbols, for example, if a subcarrier spacing of a numerology is 30 kHz. A subframe may have 56 OFDM symbols, for example, if a subcarrier spacing of a numerology is 60 kHz. A subcarrier spacing of a numerology may comprise any other frequency. A second number of resource blocks comprised in a resource grid of a carrier may depend on a bandwidth and a numerology of the carrier.

A resource block 806 may comprise 12 subcarriers. Multiple resource blocks may be grouped into a Resource Block Group (RBG) 804. A size of a RBG may depend on at least one of: a RRC message indicating a RBG size configuration; a size of a carrier bandwidth; and/or a size of a bandwidth part of a carrier. A carrier may comprise multiple bandwidth parts. A first bandwidth part of a carrier may have a different frequency location and/or a different bandwidth from a second bandwidth part of the carrier.

A base station may send (e.g., transmit), to a wireless device, a downlink control information comprising a downlink or uplink resource block assignment. A base station may send (e.g., transmit) to and/or receive from, a wireless device, data packets (e.g., transport blocks). The data packets may be scheduled on and transmitted via one or more resource blocks and one or more slots indicated by parameters in downlink control information and/or RRC message(s). A starting symbol relative to a first slot of the one or more slots may be indicated to the wireless device. A base station may send (e.g., transmit) to and/or receive from, a wireless device, data packets. The data packets may be scheduled for transmission on one or more RBGs and in one or more slots.

A base station may send (e.g., transmit), to a wireless device, downlink control information comprising a downlink assignment. The base station may send (e.g., transmit) the DCI via one or more PDCCHs. The downlink assignment may comprise parameters indicating at least one of a modulation and coding format; resource allocation; and/or HARQ information related to the DL-SCH. The resource allocation may comprise parameters of resource block allocation; and/or slot allocation. A base station may allocate (e.g., dynamically) resources to a wireless device, for example, via a Cell-Radio Network Temporary Identifier (C-RNTI) on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs, for example, in order to find possible allocation if its downlink reception is enabled. The wireless device may receive one or more downlink data packets on one or more PDSCH scheduled by the one or more PDCCHs, for example, if the wireless device successfully detects the one or more PDCCHs.

A base station may allocate Configured Scheduling (CS) resources for down link transmission to a wireless device. The base station may send (e.g., transmit) one or more RRC messages indicating a periodicity of the CS grant. The base station may send (e.g., transmit) DCI via a PDCCH addressed to a Configured Scheduling-RNTI (CS-RNTI) activating the CS resources. The DCI may comprise parameters indicating that the downlink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC messages. The CS grant may be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit), to a wireless device via one or more PDCCHs, downlink control information comprising an uplink grant. The uplink grant may comprise parameters indicating at least one of a modulation and coding format; a resource allocation; and/or HARQ information related to the UL-SCH. The resource allocation may comprise parameters of resource block allocation; and/or slot allocation. The base station may dynamically allocate resources to the wireless device via a C-RNTI on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs, for example, in order to find possible resource allocation. The wireless device may send (e.g., transmit) one or more uplink data packets via one or more PUSCH scheduled by the one or more PDCCHs, for example, if the wireless device successfully detects the one or more PDCCHs.

The base station may allocate CS resources for uplink data transmission to a wireless device. The base station may transmit one or more RRC messages indicating a periodicity of the CS grant. The base station may send (e.g., transmit) DCI via a PDCCH addressed to a CS-RNTI to activate the CS resources. The DCI may comprise parameters indicating that the uplink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC message, The CS grant may be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit) DCI and/or control signaling via a PDCCH. The DCI may comprise a format of a plurality of formats. The DCI may comprise downlink and/or uplink scheduling information (e.g., resource allocation information, HARQ related parameters, MCS), request(s) for CSI (e.g., aperiodic CQI reports), request(s) for an SRS, uplink power control commands for one or more cells, one or more timing information (e.g., TB transmission/reception timing, HARQ feedback timing, etc.), and/or the like. The DCI may indicate an uplink grant comprising transmission parameters for one or more transport blocks. The DCI may indicate a downlink assignment indicating parameters for receiving one or more transport blocks. The DCI may be used by the base station to initiate a contention-free random access at the wireless device. The base station may send (e.g., transmit) DCI comprising a slot format indicator (SFI) indicating a slot format. The base station may send (e.g., transmit) DCI comprising a preemption indication indicating the PRB(s) and/or OFDM symbol(s) in which a wireless device may assume no transmission is intended for the wireless device. The base station may send (e.g., transmit) DCI for group power control of the PUCCH, the PUSCH, and/or an SRS. DCI may correspond to an RNTI. The wireless device may obtain an RNTI after or in response to completing the initial access (e.g., C-RNTI). The base station may configure an RNTI for the wireless (e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, etc.). The wireless device may determine (e.g., compute) an RNTI (e.g., the wireless device may determine the RA-RNTI based on resources used for transmission of a preamble). An RNTI may have a pre-configured value (e.g., P-RNTI or SI-RNTI). The wireless device may monitor a group common search space which may be used by the base station for sending (e.g., transmitting) DCIs that are intended for a group of wireless devices. A group common DCI may correspond to an RNTI which is commonly configured for a group of wireless devices. The wireless device may monitor a wireless device-specific search space. A wireless device specific DCI may correspond to an RNTI configured for the wireless device.

A communications system (e.g., an NR system) may support a single beam operation and/or a multi-beam operation. In a multi-beam operation, a base station may perform a downlink beam sweeping to provide coverage for common control channels and/or downlink SS blocks, which may comprise at least a PSS, a SSS, and/or PBCH. A wireless device may measure quality of a beam pair link using one or more RSs. One or more SS blocks, or one or more CSI-RS resources (e.g., which may be associated with a CSI-RS resource index (CRI)), and/or one or more DM-RSs of a PBCH, may be used as an RS for measuring a quality of a beam pair link. The quality of a beam pair link may be based on a reference signal received power (RSRP) value, a reference signal received quality (RSRQ) value, and/or a CSI value measured on RS resources. The base station may indicate whether an RS resource, used for measuring a beam pair link quality, is quasi-co-located (QCLed) with DM-RSs of a control channel. An RS resource and DM-RSs of a control channel may be called QCLed, for example, if channel characteristics from a transmission on an RS to a wireless device, and that from a transmission on a control channel to a wireless device, are similar or the same under a configured criterion. In a multi-beam operation, a wireless device may perform an uplink beam sweeping to access a cell.

A wireless device may be configured to monitor a PDCCH on one or more beam pair links simultaneously, for example, depending on a capability of the wireless device. This monitoring may increase robustness against beam pair link blocking. A base station may send (e.g., transmit) one or more messages to configure the wireless device to monitor the PDCCH on one or more beam pair links in different PDCCH OFDM symbols. A base station may send (e.g., transmit) higher layer signaling (e.g., RRC signaling) and/or a MAC CE comprising parameters related to the Rx beam setting of the wireless device for monitoring the PDCCH on one or more beam pair links. The base station may send (e.g., transmit) an indication of a spatial QCL assumption between an DL RS antenna port(s) (e.g., a cell-specific CSI-RS, a wireless device-specific CSI-RS, an SS block, and/or a PBCH with or without DM-RSs of the PBCH) and/or DL RS antenna port(s) for demodulation of a DL control channel. Signaling for beam indication for a PDCCH may comprise MAC CE signaling, RRC signaling, DCI signaling, and/or specification-transparent and/or implicit method, and/or any combination of signaling methods.

A base station may indicate spatial QCL parameters between DL RS antenna port(s) and DM-RS antenna port(s) of a DL data channel, for example, for reception of a unicast DL data channel. The base station may send (e.g., transmit) DCI (e.g., downlink grants) comprising information indicating the RS antenna port(s). The information may indicate RS antenna port(s) that may be QCLed with the DM-RS antenna port(s). A different set of DM-RS antenna port(s) for a DL data channel may be indicated as QCL with a different set of the RS antenna port(s).

FIG. 9A shows an example of beam sweeping in a DL channel. In an RRC_INACTIVE state or RRC_IDLE state, a wireless device may assume that SS blocks form an SS burst 940, and an SS burst set 950. The SS burst set 950 may have a given periodicity. A base station 120 may send (e.g., transmit) SS blocks in multiple beams, together forming a SS burst 940, for example, in a multi-beam operation. One or more SS blocks may be sent (e.g., transmitted) on one beam. If multiple SS bursts 940 are transmitted with multiple beams, SS bursts together may form SS burst set 950.

A wireless device may use CSI-RS for estimating a beam quality of a link between a wireless device and a base station, for example, in the multi beam operation. A beam may be associated with a CSI-RS. A wireless device may (e.g., based on a RSRP measurement on CSI-RS) report a beam index, which may be indicated in a CRI for downlink beam selection and/or associated with an RSRP value of a beam. A CSI-RS may be sent (e.g., transmitted) on a CSI-RS resource, which may comprise at least one of: one or more antenna ports and/or one or more time and/or frequency radio resources. A CSI-RS resource may be configured in a cell-specific way such as by common RRC signaling, or in a wireless device-specific way such as by dedicated RRC signaling and/or L1/L2 signaling. Multiple wireless devices covered by a cell may measure a cell-specific CSI-RS resource. A dedicated subset of wireless devices covered by a cell may measure a wireless device-specific CSI-RS resource.

A CSI-RS resource may be sent (e.g., transmitted) periodically, using aperiodic transmission, or using a multi-shot or semi-persistent transmission. In a periodic transmission in FIG. 9A, a base station 120 may send (e.g., transmit) configured CSI-RS resources 940 periodically using a configured periodicity in a time domain. In an aperiodic transmission, a configured CSI-RS resource may be sent (e.g., transmitted) in a dedicated time slot. In a multi-shot and/or semi-persistent transmission, a configured CSI-RS resource may be sent (e.g., transmitted) within a configured period. Beams used for CSI-RS transmission may have a different beam width than beams used for SS-blocks transmission.

FIG. 9B shows an example of a beam management procedure, such as in an example new radio network. The base station 120 and/or the wireless device 110 may perform a downlink L1/L2 beam management procedure. One or more of the following downlink L1/L2 beam management procedures may be performed within one or more wireless devices 110 and one or more base stations 120. A P1 procedure 910 may be used to enable the wireless device 110 to measure one or more Transmission (Tx) beams associated with the base station 120, for example, to support a selection of a first set of Tx beams associated with the base station 120 and a first set of Rx beam(s) associated with the wireless device 110. A base station 120 may sweep a set of different Tx beams, for example, for beamforming at a base station 120 (such as shown in the top row, in a counter-clockwise direction). A wireless device 110 may sweep a set of different Rx beams, for example, for beamforming at a wireless device 110 (such as shown in the bottom row, in a clockwise direction). A P2 procedure 920 may be used to enable a wireless device 110 to measure one or more Tx beams associated with a base station 120, for example, to possibly change a first set of Tx beams associated with a base station 120. A P2 procedure 920 may be performed on a possibly smaller set of beams (e.g., for beam refinement) than in the P1 procedure 910. A P2 procedure 920 may be a special example of a P1 procedure 910. A P3 procedure 930 may be used to enable a wireless device 110 to measure at least one Tx beam associated with a base station 120, for example, to change a first set of Rx beams associated with a wireless device 110.

A wireless device 110 may send (e.g., transmit) one or more beam management reports to a base station 120. In one or more beam management reports, a wireless device 110 may indicate one or more beam pair quality parameters comprising one or more of: a beam identification; an RSRP; a Precoding Matrix Indicator (PMI), Channel Quality Indicator (CQI), and/or Rank Indicator (RI) of a subset of configured beams. Based on one or more beam management reports, the base station 120 may send (e.g., transmit) to a wireless device 110 a signal indicating that one or more beam pair links are one or more serving beams. The base station 120 may send (e.g., transmit) the PDCCH and the PDSCH for a wireless device 110 using one or more serving beams.

A communications network (e.g., a new radio network) may support a Bandwidth Adaptation (BA). Receive and/or transmit bandwidths that may be configured for a wireless device using a BA may not be large. Receive and/or transmit bandwidth may not be as large as a bandwidth of a cell. Receive and/or transmit bandwidths may be adjustable. A wireless device may change receive and/or transmit bandwidths, for example, to reduce (e.g., shrink) the bandwidth(s) at (e.g., during) a period of low activity such as to save power. A wireless device may change a location of receive and/or transmit bandwidths in a frequency domain, for example, to increase scheduling flexibility. A wireless device may change a subcarrier spacing, for example, to allow different services.

A Bandwidth Part (BWP) may comprise a subset of a total cell bandwidth of a cell. A base station may configure a wireless device with one or more BWPs, for example, to achieve a BA. A base station may indicate, to a wireless device, which of the one or more (configured) BWPs is an active BWP.

FIG. 10 shows an example of BWP configurations. BWPs may be configured as follows: BWP1 (1010 and 1050) with a width of 40 MHz and subcarrier spacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz and subcarrier spacing of 15 kHz; BWP3 1030 with a width of 20 MHz and subcarrier spacing of 60 kHz. Any number of BWP configurations may comprise any other width and subcarrier spacing combination.

A wireless device, configured for operation in one or more BWPs of a cell, may be configured by one or more higher layers (e.g., RRC layer). The wireless device may be configured for a cell with: a set of one or more BWPs (e.g., at most four BWPs) for reception (e.g., a DL BWP set) in a DL bandwidth by at least one parameter DL-BWP; and a set of one or more BWPs (e.g., at most four BWPs) for transmissions (e.g., UL BWP set) in an UL bandwidth by at least one parameter UL-BWP.

A base station may configure a wireless device with one or more UL and DL BWP pairs, for example, to enable BA on the PCell. To enable BA on SCells (e.g., for CA), a base station may configure a wireless device at least with one or more DL BWPs (e.g., there may be none in an UL).

An initial active DL BWP may comprise at least one of a location and number of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, for example, for a control resource set for at least one common search space. For operation on the PCell, one or more higher layer parameters may indicate at least one initial UL BWP for a random access procedure. If a wireless device is configured with a secondary carrier on a primary cell, the wireless device may be configured with an initial BWP for random access procedure on a secondary carrier.

A wireless device may expect that a center frequency for a DL BWP may be same as a center frequency for a UL BWP, for example, for unpaired spectrum operation. A base statin may semi-statically configure a wireless device for a cell with one or more parameters, for example, for a DL BWP or an UL BWP in a set of one or more DL BWPs or one or more UL BWPs, respectively. The one or more parameters may indicate one or more of following: a subcarrier spacing; a cyclic prefix; a number of contiguous PRBs; an index in the set of one or more DL BWPs and/or one or more UL BWPs; a link between a DL BWP and an UL BWP from a set of configured DL BWPs and UL BWPs; DCI detection to a PDSCH reception timing; a PDSCH reception to a HARQ-ACK transmission timing value; DCI detection to a PUSCH transmission timing value; and/or an offset of a first PRB of a DL bandwidth or an UL bandwidth, respectively, relative to a first PRB of a bandwidth.

For a DL BWP in a set of one or more DL BWPs on a PCell, a base station may configure a wireless device with one or more control resource sets for at least one type of common search space and/or one wireless device-specific search space. A base station may not configure a wireless device without a common search space on a PCell, or on a PSCell, in an active DL BWP. For an UL BWP in a set of one or more UL BWPs, a base station may configure a wireless device with one or more resource sets for one or more PUCCH transmissions.

DCI may comprise a BWP indicator field. The BWP indicator field value may indicate an active DL BWP, from a configured DL BWP set, for one or more DL receptions. The BWP indicator field value may indicate an active UL BWP, from a configured UL BWP set, for one or more UL transmissions.

For a PCell, a base station may semi-statically configure a wireless device with a default DL BWP among configured DL BWPs. If a wireless device is not provided a default DL BWP, a default BWP may be an initial active DL BWP.

A base station may configure a wireless device with a timer value for a PCell. A wireless device may start a timer (e.g., a BWP inactivity timer), for example, if a wireless device detects DCI indicating an active DL BWP, other than a default DL BWP, for a paired spectrum operation, and/or if a wireless device detects DCI indicating an active DL BWP or UL BWP, other than a default DL BWP or UL BWP, for an unpaired spectrum operation. The wireless device may increment the timer by an interval of a first value (e.g., the first value may be 1 millisecond, 0.5 milliseconds, or any other time duration), for example, if the wireless device does not detect DCI at (e.g., during) the interval for a paired spectrum operation or for an unpaired spectrum operation. The timer may expire at a time that the timer is equal to the timer value. A wireless device may switch to the default DL BWP from an active DL BWP, for example, if the timer expires.

A base station may semi-statically configure a wireless device with one or more BWPs. A wireless device may switch an active BWP from a first BWP to a second BWP, for example, after or in response to receiving DCI indicating the second BWP as an active BWP, and/or after or in response to an expiry of BWP inactivity timer (e.g., the second BWP may be a default BWP). FIG. 10 shows an example of three BWPs configured, BWP1 (1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be a default BWP. BWP1 (1010) may be an initial active BWP. A wireless device may switch an active BWP from BWP1 1010 to BWP2 1020, for example, after or in response to an expiry of the BWP inactivity timer. A wireless device may switch an active BWP from BWP2 1020 to BWP3 1030, for example, after or in response to receiving DCI indicating BWP3 1030 as an active BWP. Switching an active BWP from BWP3 1030 to BWP2 1040 and/or from BWP2 1040 to BWP1 1050 may be after or in response to receiving DCI indicating an active BWP, and/or after or in response to an expiry of BWP inactivity timer.

Wireless device procedures on a secondary cell may be same as on a primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell, for example, if a wireless device is configured for a secondary cell with a default DL BWP among configured DL BWPs and a timer value. A wireless device may use an indicated DL BWP and an indicated UL BWP on a secondary cell as a respective first active DL BWP and first active UL BWP on a secondary cell or carrier, for example, if a base station configures a wireless device with a first active DL BWP and a first active UL BWP on a secondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows using a multi connectivity (e.g., dual connectivity, multi connectivity, tight interworking, and/or the like). FIG. 11A shows an example of a protocol structure of a wireless device 110 (e.g., UE) with CA and/or multi connectivity. FIG. 11B shows an example of a protocol structure of multiple base stations with CA and/or multi connectivity. The multiple base stations may comprise a master node, MN 1130 (e.g., a master node, a master base station, a master gNB, a master eNB, and/or the like) and a secondary node, SN 1150 (e.g., a secondary node, a secondary base station, a secondary gNB, a secondary eNB, and/or the like). A master node 1130 and a secondary node 1150 may co-work to communicate with a wireless device 110.

If multi connectivity is configured for a wireless device 110, the wireless device 110, which may support multiple reception and/or transmission functions in an RRC connected state, may be configured to utilize radio resources provided by multiple schedulers of a multiple base stations. Multiple base stations may be inter-connected via a non-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and/or the like). A base station involved in multi connectivity for a certain wireless device may perform at least one of two different roles: a base station may act as a master base station or act as a secondary base station. In multi connectivity, a wireless device may be connected to one master base station and one or more secondary base stations. A master base station (e.g., the MN 1130) may provide a master cell group (MCG) comprising a primary cell and/or one or more secondary cells for a wireless device (e.g., the wireless device 110). A secondary base station (e.g., the SN 1150) may provide a secondary cell group (SCG) comprising a primary secondary cell (PSCell) and/or one or more secondary cells for a wireless device (e.g., the wireless device 110).

In multi connectivity, a radio protocol architecture that a bearer uses may depend on how a bearer is setup. Three different types of bearer setup options may be supported: an MCG bearer, an SCG bearer, and/or a split bearer. A wireless device may receive and/or send (e.g., transmit) packets of an MCG bearer via one or more cells of the MCG. A wireless device may receive and/or send (e.g., transmit) packets of an SCG bearer via one or more cells of an SCG. Multi-connectivity may indicate having at least one bearer configured to use radio resources provided by the secondary base station. Multi-connectivity may or may not be configured and/or implemented.

A wireless device (e.g., wireless device 110) may send (e.g., transmit) and/or receive: packets of an MCG bearer via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC 1114), and a MAC layer (e.g., MN MAC 1118); packets of a split bearer via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112), one of a master or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116), and one of a master or secondary MAC layer (e.g., MN MAC 1118, SN MAC 1119); and/or packets of an SCG bearer via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC 1117), and a MAC layer (e.g., MN MAC 1119).

A master base station (e.g., MN 1130) and/or a secondary base station (e.g., SN 1150) may send (e.g., transmit) and/or receive: packets of an MCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1121, NR PDCP 1142), a master node RLC layer (e.g., MN RLC 1124, MN RLC 1125), and a master node MAC layer (e.g., MN MAC 1128); packets of an SCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1122, NR PDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147), and a secondary node MAC layer (e.g., SN MAC 1148); packets of a split bearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1123, NR PDCP 1141), a master or secondary node RLC layer (e.g., MN RLC 1126, SN RLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAC layer (e.g., MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MAC entities, such as one MAC entity (e.g., MN MAC 1118) for a master base station, and other MAC entities (e.g., SN MAC 1119) for a secondary base station. In multi-connectivity, a configured set of serving cells for a wireless device may comprise two subsets: an MCG comprising serving cells of a master base station, and SCGs comprising serving cells of a secondary base station. For an SCG, one or more of following configurations may be used. At least one cell of an SCG may have a configured UL CC and at least one cell of a SCG, named as primary secondary cell (e.g., PSCell, PCell of SCG, PCell), and may be configured with PUCCH resources. If an SCG is configured, there may be at least one SCG bearer or one split bearer. After or upon detection of a physical layer problem or a random access problem on a PSCell, or a number of NR RLC retransmissions has been reached associated with the SCG, or after or upon detection of an access problem on a PSCell associated with (e.g., during) a SCG addition or an SCG change: an RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of an SCG may be stopped, a master base station may be informed by a wireless device of a SCG failure type, a DL data transfer over a master base station may be maintained (e.g., for a split bearer). An NR RLC acknowledged mode (AM) bearer may be configured for a split bearer. A PCell and/or a PSCell may not be deactivated. A PSCell may be changed with a SCG change procedure (e.g., with security key change and a RACH procedure). A bearer type change between a split bearer and a SCG bearer, and/or simultaneous configuration of a SCG and a split bearer, may or may not be supported.

With respect to interactions between a master base station and a secondary base stations for multi-connectivity, one or more of the following may be used. A master base station and/or a secondary base station may maintain RRM measurement configurations of a wireless device. A master base station may determine (e.g., based on received measurement reports, traffic conditions, and/or bearer types) to request a secondary base station to provide additional resources (e.g., serving cells) for a wireless device. After or upon receiving a request from a master base station, a secondary base station may create and/or modify a container that may result in a configuration of additional serving cells for a wireless device (or decide that the secondary base station has no resource available to do so). For a wireless device capability coordination, a master base station may provide (e.g., all or a part of) an AS configuration and wireless device capabilities to a secondary base station. A master base station and a secondary base station may exchange information about a wireless device configuration such as by using RRC containers (e.g., inter-node messages) carried via Xn messages. A secondary base station may initiate a reconfiguration of the secondary base station existing serving cells (e.g., PUCCH towards the secondary base station). A secondary base station may decide which cell is a PSCell within a SCG. A master base station may or may not change content of RRC configurations provided by a secondary base station. A master base station may provide recent (and/or the latest) measurement results for SCG cell(s), for example, if an SCG addition and/or an SCG SCell addition occurs. A master base station and secondary base stations may receive information of SFN and/or subframe offset of each other from an OAM and/or via an Xn interface (e.g., for a purpose of DRX alignment and/or identification of a measurement gap). Dedicated RRC signaling may be used for sending required system information of a cell as for CA, for example, if adding a new SCG SCell, except for an SFN acquired from an MIB of a PSCell of a SCG.

FIG. 12 shows an example of a random access procedure. One or more events may trigger a random access procedure. For example, one or more events may be at least one of following: initial access from RRC_IDLE, RRC connection re-establishment procedure, handover, DL or UL data arrival in (e.g., during) a state of RRC_CONNECTED (e.g., if UL synchronization status is non-synchronized), transition from RRC_Inactive, and/or request for other system information. A PDCCH order, a MAC entity, and/or a beam failure indication may initiate a random access procedure.

A random access procedure may comprise or be one of at least a contention based random access procedure and/or a contention free random access procedure. A contention based random access procedure may comprise one or more Msg 1 1220 transmissions, one or more Msg2 1230 transmissions, one or more Msg3 1240 transmissions, and contention resolution 1250. A contention free random access procedure may comprise one or more Msg 1 1220 transmissions and one or more Msg2 1230 transmissions. One or more of Msg 1 1220, Msg 2 1230, Msg 3 1240, and/or contention resolution 1250 may be transmitted in the same step. A two-step random access procedure, for example, may comprise a first transmission (e.g., Msg A) and a second transmission (e.g., Msg B). The first transmission (e.g., Msg A) may comprise transmitting, by a wireless device (e.g., wireless device 110) to a base station (e.g., base station 120), one or more messages indicating an equivalent and/or similar contents of Msg1 1220 and Msg3 1240 of a four-step random access procedure. The second transmission (e.g., Msg B) may comprise transmitting, by the base station (e.g., base station 120) to a wireless device (e.g., wireless device 110) after or in response to the first message, one or more messages indicating an equivalent and/or similar content of Msg2 1230 and contention resolution 1250 of a four-step random access procedure.

A base station may send (e.g., transmit, unicast, multicast, broadcast, etc.), to a wireless device, a RACH configuration 1210 via one or more beams. The RACH configuration 1210 may comprise one or more parameters indicating at least one of following: an available set of PRACH resources for a transmission of a random access preamble, initial preamble power (e.g., random access preamble initial received target power), an RSRP threshold for a selection of a SS block and corresponding PRACH resource, a power-ramping factor (e.g., random access preamble power ramping step), a random access preamble index, a maximum number of preamble transmissions, preamble group A and group B, a threshold (e.g., message size) to determine the groups of random access preambles, a set of one or more random access preambles for a system information request and corresponding PRACH resource(s) (e.g., if any), a set of one or more random access preambles for a beam failure recovery (BFR) procedure and corresponding PRACH resource(s) (e.g., if any), a time window to monitor RA response(s), a time window to monitor response(s) on a BFR procedure, and/or a contention resolution timer.

The Msg1 1220 may comprise one or more transmissions of a random access preamble. For a contention based random access procedure, a wireless device may select an SS block with an RSRP above the RSRP threshold. If random access preambles group B exists, a wireless device may select one or more random access preambles from a group A or a group B, for example, depending on a potential Msg3 1240 size. If a random access preambles group B does not exist, a wireless device may select the one or more random access preambles from a group A. A wireless device may select a random access preamble index randomly (e.g., with equal probability or a normal distribution) from one or more random access preambles associated with a selected group. If a base station semi-statically configures a wireless device with an association between random access preambles and SS blocks, the wireless device may select a random access preamble index randomly with equal probability from one or more random access preambles associated with a selected SS block and a selected group.

A wireless device may initiate a contention free random access procedure, for example, based on a beam failure indication from a lower layer. A base station may semi-statically configure a wireless device with one or more contention free PRACH resources for a BFR procedure associated with at least one of SS blocks and/or CSI-RSs. A wireless device may select a random access preamble index corresponding to a selected SS block or a CSI-RS from a set of one or more random access preambles for a BFR procedure, for example, if at least one of the SS blocks with an RSRP above a first RSRP threshold amongst associated SS blocks is available, and/or if at least one of CSI-RSs with a RSRP above a second RSRP threshold amongst associated CSI-RSs is available.

A wireless device may receive, from a base station, a random access preamble index via PDCCH or RRC for a contention free random access procedure. The wireless device may select a random access preamble index, for example, if a base station does not configure a wireless device with at least one contention free PRACH resource associated with SS blocks or CSI-RS. The wireless device may select the at least one SS block and/or select a random access preamble corresponding to the at least one SS block, for example, if a base station configures the wireless device with one or more contention free PRACH resources associated with SS blocks and/or if at least one SS block with a RSRP above a first RSRP threshold amongst associated SS blocks is available. The wireless device may select the at least one CSI-RS and/or select a random access preamble corresponding to the at least one CSI-RS, for example, if a base station configures a wireless device with one or more contention free PRACH resources associated with CSI-RSs and/or if at least one CSI-RS with a RSRP above a second RSPR threshold amongst the associated CSI-RSs is available.

A wireless device may perform one or more Msg1 1220 transmissions, for example, by sending (e.g., transmitting) the selected random access preamble. The wireless device may determine a PRACH occasion from one or more PRACH occasions corresponding to a selected SS block, for example, if the wireless device selects an SS block and is configured with an association between one or more PRACH occasions and/or one or more SS blocks. The wireless device may determine a PRACH occasion from one or more PRACH occasions corresponding to a selected CSI-RS, for example, if the wireless device selects a CSI-RS and is configured with an association between one or more PRACH occasions and one or more CSI-RSs. The wireless device may send (e.g., transmit), to a base station, a selected random access preamble via a selected PRACH occasions. The wireless device may determine a transmit power for a transmission of a selected random access preamble at least based on an initial preamble power and a power-ramping factor. The wireless device may determine an RA-RNTI associated with a selected PRACH occasion in which a selected random access preamble is sent (e.g., transmitted). The wireless device may not determine an RA-RNTI for a BFR procedure. The wireless device may determine an RA-RNTI at least based on an index of a first OFDM symbol, an index of a first slot of a selected PRACH occasions, and/or an uplink carrier index for a transmission of Msg1 1220.

A wireless device may receive, from a base station, a random access response, Msg 2 1230. The wireless device may start a time window (e.g., ra-ResponseWindow) to monitor a random access response. For a BFR procedure, the base station may configure the wireless device with a different time window (e.g., bfr-ResponseWindow) to monitor response on a BFR procedure. The wireless device may start a time window (e.g., ra-ResponseWindow or bfr-ResponseWindow) at a start of a first PDCCH occasion, for example, after a fixed duration of one or more symbols from an end of a preamble transmission. If the wireless device sends (e.g., transmits) multiple preambles, the wireless device may start a time window at a start of a first PDCCH occasion after a fixed duration of one or more symbols from an end of a first preamble transmission. The wireless device may monitor a PDCCH of a cell for at least one random access response identified by a RA-RNTI, or for at least one response to a BFR procedure identified by a C-RNTI, at a time that a timer for a time window is running.

A wireless device may determine that a reception of random access response is successful, for example, if at least one random access response comprises a random access preamble identifier corresponding to a random access preamble sent (e.g., transmitted) by the wireless device. The wireless device may determine that the contention free random access procedure is successfully completed, for example, if a reception of a random access response is successful. The wireless device may determine that a contention free random access procedure is successfully complete, for example, if a contention free random access procedure is triggered for a BFR procedure and if a PDCCH transmission is addressed to a C-RNTI. The wireless device may determine that the random access procedure is successfully completed, and may indicate a reception of an acknowledgement for a system information request to upper layers, for example, if at least one random access response comprises a random access preamble identifier. The wireless device may stop sending (e.g., transmitting) remaining preambles (if any) after or in response to a successful reception of a corresponding random access response, for example, if the wireless device has signaled multiple preamble transmissions.

The wireless device may perform one or more Msg 3 1240 transmissions, for example, after or in response to a successful reception of random access response (e.g., for a contention based random access procedure). The wireless device may adjust an uplink transmission timing, for example, based on a timing advanced command indicated by a random access response. The wireless device may send (e.g., transmit) one or more transport blocks, for example, based on an uplink grant indicated by a random access response. Subcarrier spacing for PUSCH transmission for Msg3 1240 may be provided by at least one higher layer (e.g., RRC) parameter. The wireless device may send (e.g., transmit) a random access preamble via a PRACH, and Msg3 1240 via PUSCH, on the same cell. A base station may indicate an UL BWP for a PUSCH transmission of Msg3 1240 via system information block. The wireless device may use HARQ for a retransmission of Msg 3 1240.

Multiple wireless devices may perform Msg 1 1220, for example, by sending (e.g., transmitting) the same preamble to a base station. The multiple wireless devices may receive, from the base station, the same random access response comprising an identity (e.g., TC-RNTI). Contention resolution (e.g., comprising the wireless device 110 receiving contention resolution 1250) may be used to increase the likelihood that a wireless device does not incorrectly use an identity of another wireless device. The contention resolution 1250 may be based on, for example, a C-RNTI on a PDCCH, and/or a wireless device contention resolution identity on a DL-SCH. If a base station assigns a C-RNTI to a wireless device, the wireless device may perform contention resolution (e.g., comprising receiving contention resolution 1250), for example, based on a reception of a PDCCH transmission that is addressed to the C-RNTI. The wireless device may determine that contention resolution is successful, and/or that a random access procedure is successfully completed, for example, after or in response to detecting a C-RNTI on a PDCCH. If a wireless device has no valid C-RNTI, a contention resolution may be addressed by using a TC-RNTI. If a MAC PDU is successfully decoded and a MAC PDU comprises a wireless device contention resolution identity MAC CE that matches or otherwise corresponds with the CCCH SDU sent (e.g., transmitted) in Msg3 1250, the wireless device may determine that the contention resolution (e.g., comprising contention resolution 1250) is successful and/or the wireless device may determine that the random access procedure is successfully completed.

FIG. 13 shows an example structure for MAC entities. A wireless device may be configured to operate in a multi-connectivity mode. A wireless device in RRC_CONNECTED with multiple Rx/Tx may be configured to utilize radio resources provided by multiple schedulers that may be located in a plurality of base stations. The plurality of base stations may be connected via a non-ideal or ideal backhaul over the Xn interface. A base station in a plurality of base stations may act as a master base station or as a secondary base station. A wireless device may be connected to and/or in communication with, for example, one master base station and one or more secondary base stations. A wireless device may be configured with multiple MAC entities, for example, one MAC entity for a master base station, and one or more other MAC entities for secondary base station(s). A configured set of serving cells for a wireless device may comprise two subsets: an MCG comprising serving cells of a master base station, and one or more SCGs comprising serving cells of a secondary base station(s). FIG. 13 shows an example structure for MAC entities in which a MCG and a SCG are configured for a wireless device.

At least one cell in a SCG may have a configured UL CC. A cell of the at least one cell may comprise a PSCell or a PCell of a SCG, or a PCell. A PSCell may be configured with PUCCH resources. There may be at least one SCG bearer, or one split bearer, for a SCG that is configured. After or upon detection of a physical layer problem or a random access problem on a PSCell, after or upon reaching a number of RLC retransmissions associated with the SCG, and/or after or upon detection of an access problem on a PSCell associated with (e.g., during) a SCG addition or a SCG change: an RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of a SCG may be stopped, and/or a master base station may be informed by a wireless device of a SCG failure type and DL data transfer over a master base station may be maintained.

A MAC sublayer may provide services such as data transfer and radio resource allocation to upper layers (e.g., 1310 or 1320). A MAC sublayer may comprise a plurality of MAC entities (e.g., 1350 and 1360). A MAC sublayer may provide data transfer services on logical channels. To accommodate different kinds of data transfer services, multiple types of logical channels may be defined. A logical channel may support transfer of a particular type of information. A logical channel type may be defined by what type of information (e.g., control or data) is transferred. BCCH, PCCH, CCCH and/or DCCH may be control channels, and DTCH may be a traffic channel. A first MAC entity (e.g., 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCH, and/or MAC control elements. A second MAC entity (e.g., 1320) may provide services on BCCH, DCCH, DTCH, and/or MAC control elements.

A MAC sublayer may expect from a physical layer (e.g., 1330 or 1340) services such as data transfer services, signaling of HARQ feedback, and/or signaling of scheduling request or measurements (e.g., CQI). In dual connectivity, two MAC entities may be configured for a wireless device: one for a MCG and one for a SCG. A MAC entity of a wireless device may handle a plurality of transport channels. A first MAC entity may handle first transport channels comprising a PCCH of a MCG, a first BCH of the MCG, one or more first DL-SCHs of the MCG, one or more first UL-SCHs of the MCG, and/or one or more first RACHs of the MCG. A second MAC entity may handle second transport channels comprising a second BCH of a SCG, one or more second DL-SCHs of the SCG, one or more second UL-SCHs of the SCG, and/or one or more second RACHs of the SCG.

If a MAC entity is configured with one or more SCells, there may be multiple DL-SCHs, multiple UL-SCHs, and/or multiple RACHs per MAC entity. There may be one DL-SCH and/or one UL-SCH on an SpCell. There may be one DL-SCH, zero or one UL-SCH, and/or zero or one RACH for an SCell. A DL-SCH may support receptions using different numerologies and/or TTI duration within a MAC entity. A UL-SCH may support transmissions using different numerologies and/or TTI duration within the MAC entity.

A MAC sublayer may support different functions. The MAC sublayer may control these functions with a control (e.g., Control 1355 and/or Control 1365) element. Functions performed by a MAC entity may comprise one or more of: mapping between logical channels and transport channels (e.g., in uplink or downlink), multiplexing (e.g., (De-) Multiplexing 1352 and/or (De-) Multiplexing 1362) of MAC SDUs from one or different logical channels onto transport blocks (TBs) to be delivered to the physical layer on transport channels (e.g., in uplink), demultiplexing (e.g., (De-) Multiplexing 1352 and/or (De-) Multiplexing 1362) of MAC SDUs to one or different logical channels from transport blocks (TBs) delivered from the physical layer on transport channels (e.g., in downlink), scheduling information reporting (e.g., in uplink), error correction through HARQ in uplink and/or downlink (e.g., 1363), and logical channel prioritization in uplink (e.g., Logical Channel Prioritization 1351 and/or Logical Channel Prioritization 1361). A MAC entity may handle a random access process (e.g., Random Access Control 1354 and/or Random Access Control 1364).

FIG. 14 shows an example of a RAN architecture comprising one or more base stations. A protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and/or PHY) may be supported at a node. A base station (e.g., gNB 120A and/or 120B) may comprise a base station central unit (CU) (e.g., gNB-CU 1420A or 1420B) and at least one base station distributed unit (DU) (e.g., gNB-DU 1430A, 1430B, 1430C, and/or 1430D), for example, if a functional split is configured. Upper protocol layers of a base station may be located in a base station CU, and lower layers of the base station may be located in the base station DUs. An F1 interface (e.g., CU-DU interface) connecting a base station CU and base station DUs may be an ideal or non-ideal backhaul. F1-C may provide a control plane connection over an F1 interface, and F1-U may provide a user plane connection over the F1 interface. An Xn interface may be configured between base station CUs.

A base station CU may comprise an RRC function, an SDAP layer, and/or a PDCP layer. Base station DUs may comprise an RLC layer, a MAC layer, and/or a PHY layer. Various functional split options between a base station CU and base station DUs may be possible, for example, by locating different combinations of upper protocol layers (e.g., RAN functions) in a base station CU and different combinations of lower protocol layers (e.g., RAN functions) in base station DUs. A functional split may support flexibility to move protocol layers between a base station CU and base station DUs, for example, depending on service requirements and/or network environments.

Functional split options may be configured per base station, per base station CU, per base station DU, per wireless device, per bearer, per slice, and/or with other granularities. In a per base station CU split, a base station CU may have a fixed split option, and base station DUs may be configured to match a split option of a base station CU. In a per base station DU split, a base station DU may be configured with a different split option, and a base station CU may provide different split options for different base station DUs. In a per wireless device split, a base station (e.g., a base station CU and at least one base station DUs) may provide different split options for different wireless devices. In a per bearer split, different split options may be utilized for different bearers. In a per slice splice, different split options may be used for different slices.

FIG. 15 shows example RRC state transitions of a wireless device. A wireless device may be in at least one RRC state among an RRC connected state (e.g., RRC Connected 1530, RRC_Connected, etc.), an RRC idle state (e.g., RRC Idle 1510, RRC_Idle, etc.), and/or an RRC inactive state (e.g., RRC Inactive 1520, RRC_Inactive, etc.). In an RRC connected state, a wireless device may have at least one RRC connection with at least one base station (e.g., gNB and/or eNB), which may have a context of the wireless device (e.g., UE context). A wireless device context (e.g., UE context) may comprise at least one of an access stratum context, one or more radio link configuration parameters, bearer (e.g., data radio bearer (DRB), signaling radio bearer (SRB), logical channel, QoS flow, PDU session, and/or the like) configuration information, security information, PHY/MAC/RLC/PDCP/SDAP layer configuration information, and/or the like configuration information for a wireless device. In an RRC idle state, a wireless device may not have an RRC connection with a base station, and a context of the wireless device may not be stored in a base station. In an RRC inactive state, a wireless device may not have an RRC connection with a base station. A context of a wireless device may be stored in a base station, which may comprise an anchor base station (e.g., a last serving base station).

A wireless device may transition an RRC state (e.g., UE RRC state) between an RRC idle state and an RRC connected state in both ways (e.g., connection release 1540 or connection establishment 1550; and/or connection reestablishment) and/or between an RRC inactive state and an RRC connected state in both ways (e.g., connection inactivation 1570 or connection resume 1580). A wireless device may transition its RRC state from an RRC inactive state to an RRC idle state (e.g., connection release 1560).

An anchor base station may be a base station that may keep a context of a wireless device (e.g., UE context) at least at (e.g., during) a time period that the wireless device stays in a RAN notification area (RNA) of an anchor base station, and/or at (e.g., during) a time period that the wireless device stays in an RRC inactive state. An anchor base station may comprise a base station that a wireless device in an RRC inactive state was most recently connected to in a latest RRC connected state, and/or a base station in which a wireless device most recently performed an RNA update procedure. An RNA may comprise one or more cells operated by one or more base stations. A base station may belong to one or more RNAs. A cell may belong to one or more RNAs.

A wireless device may transition, in a base station, an RRC state (e.g., UE RRC state) from an RRC connected state to an RRC inactive state. The wireless device may receive RNA information from the base station. RNA information may comprise at least one of an RNA identifier, one or more cell identifiers of one or more cells of an RNA, a base station identifier, an IP address of the base station, an AS context identifier of the wireless device, a resume identifier, and/or the like.

An anchor base station may broadcast a message (e.g., RAN paging message) to base stations of an RNA to reach to a wireless device in an RRC inactive state. The base stations receiving the message from the anchor base station may broadcast and/or multicast another message (e.g., paging message) to wireless devices in their coverage area, cell coverage area, and/or beam coverage area associated with the RNA via an air interface.

A wireless device may perform an RNA update (RNAU) procedure, for example, if the wireless device is in an RRC inactive state and moves into a new RNA. The RNAU procedure may comprise a random access procedure by the wireless device and/or a context retrieve procedure (e.g., UE context retrieve). A context retrieve procedure may comprise: receiving, by a base station from a wireless device, a random access preamble; and requesting and/or receiving (e.g., fetching), by a base station, a context of the wireless device (e.g., UE context) from an old anchor base station. The requesting and/or receiving (e.g., fetching) may comprise: sending a retrieve context request message (e.g., UE context request message) comprising a resume identifier to the old anchor base station and receiving a retrieve context response message comprising the context of the wireless device from the old anchor base station.

A wireless device in an RRC inactive state may select a cell to camp on based on at least a measurement result for one or more cells, a cell in which a wireless device may monitor an RNA paging message, and/or a core network paging message from a base station. A wireless device in an RRC inactive state may select a cell to perform a random access procedure to resume an RRC connection and/or to send (e.g., transmit) one or more packets to a base station (e.g., to a network). The wireless device may initiate a random access procedure to perform an RNA update procedure, for example, if a cell selected belongs to a different RNA from an RNA for the wireless device in an RRC inactive state. The wireless device may initiate a random access procedure to send (e.g., transmit) one or more packets to a base station of a cell that the wireless device selects, for example, if the wireless device is in an RRC inactive state and has one or more packets (e.g., in a buffer) to send (e.g., transmit) to a network. A random access procedure may be performed with two messages (e.g., 2-stage or 2-step random access) and/or four messages (e.g., 4-stage or 4-step random access) between the wireless device and the base station.

A base station receiving one or more uplink packets from a wireless device in an RRC inactive state may request and/or receive (e.g., fetch) a context of a wireless device (e.g., UE context), for example, by sending (e.g., transmitting) a retrieve context request message for the wireless device to an anchor base station of the wireless device based on at least one of an AS context identifier, an RNA identifier, a base station identifier, a resume identifier, and/or a cell identifier received from the wireless device. A base station may send (e.g., transmit) a path switch request for a wireless device to a core network entity (e.g., AMF, MME, and/or the like), for example, after or in response to requesting and/or receiving (e.g., fetching) a context. A core network entity may update a downlink tunnel endpoint identifier for one or more bearers established for the wireless device between a user plane core network entity (e.g., UPF, S-GW, and/or the like) and a RAN node (e.g., the base station), such as by changing a downlink tunnel endpoint identifier from an address of the anchor base station to an address of the base station).

A base station may send (e.g., transmit) one or more MAC PDUs to a wireless device. A MAC PDU may comprise a bit string that may be byte aligned (e.g., multiple of eight bits) in length. Bit strings may be represented by tables in which the most significant bit is the leftmost bit of the first line of the table, and the least significant bit is the rightmost bit on the last line of the table. The bit string may be read from the left to right, and then, in the reading order of the lines. The bit order of a parameter field within a MAC PDU may be represented with the first and most significant bit in the leftmost bit, and with the last and least significant bit in the rightmost bit.

A MAC SDU may comprise a bit string that is byte aligned (e.g., multiple of eight bits) in length. A MAC SDU may be included in a MAC PDU, for example, from the first bit onward. In an example, a MAC CE may be a bit string that is byte aligned (e.g., multiple of eight bits) in length. A MAC subheader may be a bit string that is byte aligned (e.g., multiple of eight bits) in length. A MAC subheader may be placed immediately in front of the corresponding MAC SDU, MAC CE, and/or padding. A MAC entity may ignore a value of reserved bits in a DL MAC PDU.

A MAC PDU may comprise one or more MAC subPDUs. A MAC subPDU of the one or more MAC subPDUs may comprise at least one of: a MAC subheader only (e.g., including padding); a MAC subheader and a MAC SDU; a MAC subheader and a MAC CE; and/or a MAC subheader and padding. The MAC SDU may be of variable size. A MAC subheader may correspond to a MAC SDU, a MAC CE, and/or padding.

A MAC subheader may comprise: an R field comprising one bit; an F field with one bit in length; an LCID field with multiple bits in length; an L field with multiple bits in length, for example, if the MAC subheader corresponds to a MAC SDU, a variable-sized MAC CE, and/or padding.

FIG. 16A shows an example of a MAC subheader comprising an eight-bit L field. The LCID field may have six bits in length. The L field may have eight bits in length.

FIG. 16B shows an example of a MAC subheader with a sixteen-bit L field. The LCID field may have six bits in length. The L field may have sixteen bits in length. A MAC subheader may comprise: a R field comprising two bits in length; and an LCID field comprising multiple bits in length (e.g., if the MAC subheader corresponds to a fixed sized MAC CE), and/or padding.

FIG. 16C shows an example of the MAC subheader. The LCID field may comprise six bits in length, and the R field may comprise two bits in length.

FIG. 17A shows an example of a DL MAC PDU. Multiple MAC CEs may be placed together. A MAC subPDU comprising MAC CE may be placed before any MAC subPDU comprising a MAC SDU, and/or before a MAC subPDU comprising padding.

FIG. 17B shows an example of a UL MAC PDU. Multiple MAC CEs may be placed together. A MAC subPDU comprising a MAC CE may be placed after all MAC subPDU comprising a MAC SDU. The MAC subPDU may be placed before a MAC subPDU comprising padding.

FIG. 18A shows examples of multiple LCIDs associated with the one or more MAC CEs. A MAC entity of a base station may send (e.g., transmit) to a MAC entity of a wireless device one or more MAC CEs. The one or more MAC CEs may comprise at least one of: a wireless device (e.g., UE) contention resolution identity MAC CE; a timing advance command MAC CE; a DRX command MAC CE; a long DRX command MAC CE; an SCell activation and/or deactivation MAC CE (e.g., 1 Octet); an SCell activation and/or deactivation MAC CE (e.g., 4 Octet); and/or a duplication activation and/or deactivation MAC CE. A MAC CE may comprise an LCID in the corresponding MAC subheader. Different MAC CEs may have different LCID in the corresponding MAC subheader. An LCID with 111011 in a MAC subheader may indicate a MAC CE associated with the MAC subheader is a long DRX command MAC CE.

FIG. 18B shows further examples of LCIDs associated with one or more MAC CEs. The MAC entity of the wireless device may send (e.g., transmit), to the MAC entity of the base station, one or more MAC CEs. The one or more MAC CEs may comprise at least one of: a short buffer status report (BSR) MAC CE; a long BSR MAC CE; a C-RNTI MAC CE; a configured grant confirmation MAC CE; a single entry power headroom report (PHR) MAC CE; a multiple entry PHR MAC CE; a short truncated BSR; and/or a long truncated BSR. A MAC CE may comprise an LCID in the corresponding MAC subheader. Different MAC CEs may have different LCIDs in the corresponding MAC subheader. The LCID with 111011 in a MAC subheader may indicate a MAC CE associated with the MAC subheader is a short-truncated command MAC CE.

Two or more component carriers (CCs) may be aggregated, for example, in a carrier aggregation (CA). A wireless device may simultaneously receive and/or transmit on one or more CCs, for example, depending on capabilities of the wireless device. The CA may be supported for contiguous CCs. The CA may be supported for non-contiguous CCs.

A wireless device may have one RRC connection with a network, for example, if configured with CA. At (e.g., during) an RRC connection establishment, re-establishment and/or handover, a cell providing a NAS mobility information may be a serving cell. At (e.g., during) an RRC connection re-establishment and/or handover procedure, a cell providing a security input may be a serving cell. The serving cell may be referred to as a primary cell (PCell). A base station may send (e.g., transmit), to a wireless device, one or more messages comprising configuration parameters of a plurality of one or more secondary cells (SCells), for example, depending on capabilities of the wireless device.

A base station and/or a wireless device may use an activation and/or deactivation mechanism of an SCell for an efficient battery consumption, for example, if the base station and/or the wireless device is configured with CA. A base station may activate or deactivate at least one of the one or more SCells, for example, if the wireless device is configured with one or more SCells. The SCell may be deactivated, for example, after or upon configuration of an SCell.

A wireless device may activate and/or deactivate an SCell, for example, after or in response to receiving an SCell activation and/or deactivation MAC CE. A base station may send (e.g., transmit), to a wireless device, one or more messages comprising an sCellDeactivationTimer timer. The wireless device may deactivate an SCell, for example, after or in response to an expiry of the sCellDeactivationTimer timer.

A wireless device may activate an SCell, for example, if the wireless device receives an SCell activation/deactivation MAC CE activating an SCell. The wireless device may perform operations (e.g., after or in response to the activating the SCell) that may comprise: SRS transmissions on the SCell; CQI, PMI, RI, and/or CRI reporting for the SCell on a PCell; PDCCH monitoring on the SCell; PDCCH monitoring for the SCell on the PCell; and/or PUCCH transmissions on the SCell.

The wireless device may start and/or restart a timer (e.g., an sCellDeactivationTimer timer) associated with the SCell, for example, after or in response to activating the SCell. The wireless device may start the timer (e.g., sCellDeactivationTimer timer) in the slot, for example, if the SCell activation/deactivation MAC CE has been received. The wireless device may initialize and/or re-initialize one or more suspended configured uplink grants of a configured grant Type 1 associated with the SCell according to a stored configuration, for example, after or in response to activating the SCell. The wireless device may trigger a PHR, for example, after or in response to activating the SCell.

The wireless device may deactivate the activated SCell, for example, if the wireless device receives an SCell activation/deactivation MAC CE deactivating an activated SCell. The wireless device may deactivate the activated SCell, for example, if a timer (e.g., an sCellDeactivationTimer timer) associated with an activated SCell expires. The wireless device may stop the timer (e.g., sCellDeactivationTimer timer) associated with the activated SCell, for example, after or in response to deactivating the activated SCell. The wireless device may clear one or more configured downlink assignments and/or one or more configured uplink grant Type 2 associated with the activated SCell, for example, after or in response to the deactivating the activated SCell. The wireless device may suspend one or more configured uplink grant Type 1 associated with the activated SCell, for example, after or in response to deactivating the activated SCell. The wireless device may flush HARQ buffers associated with the activated SCell.

A wireless device may not perform certain operations, for example, if an SCell is deactivated. The wireless device may not perform one or more of the following operations if an SCell is deactivated: transmitting SRS on the SCell; reporting CQI, PMI, RI, and/or CRI for the SCell on a PCell; transmitting on UL-SCH on the SCell; transmitting on a RACH on the SCell; monitoring at least one first PDCCH on the SCell; monitoring at least one second PDCCH for the SCell on the PCell; and/or transmitting a PUCCH on the SCell.

A wireless device may restart a timer (e.g., an sCellDeactivationTimer timer) associated with the activated SCell, for example, if at least one first PDCCH on an activated S Cell indicates an uplink grant or a downlink assignment. A wireless device may restart a timer (e.g., an sCellDeactivationTimer timer) associated with the activated SCell, for example, if at least one second PDCCH on a serving cell (e.g. a PCell or an SCell configured with PUCCH, such as a PUCCH SCell) scheduling the activated SCell indicates an uplink grant and/or a downlink assignment for the activated SCell. A wireless device may abort the ongoing random access procedure on the SCell, for example, if an SCell is deactivated and/or if there is an ongoing random access procedure on the SCell.

FIG. 18A shows first examples of LCIDs. FIG. 18B shows second examples of LCIDs. The left columns comprise indices. The right columns comprises corresponding LCID values for each index.

FIG. 19A shows an example of an SCell activation/deactivation MAC CE of one octet. A first MAC PDU subheader comprising a first LCID may identify the SCell activation/deactivation MAC CE of one octet. An SCell activation/deactivation MAC CE of one octet may have a fixed size. The SCell activation/deactivation MAC CE of one octet may comprise a single octet. The single octet may comprise a first number of C-fields (e.g., seven) and a second number of R-fields (e.g., one).

FIG. 19B shows an example of an SCell Activation/Deactivation MAC CE of four octets. A second MAC PDU subheader with a second LCID may identify the SCell Activation/Deactivation MAC CE of four octets. An SCell activation/deactivation MAC CE of four octets may have a fixed size. The SCell activation/deactivation MAC CE of four octets may comprise four octets. The four octets may comprise a third number of C-fields (e.g., 31) and a fourth number of R-fields (e.g., 1). A C_i field may indicate an activation/deactivation status of an SCell with an SCell index i. An SCell with an SCell index i may be activated, for example, if the C_i field is set to one. An SCell with an SCell index i may be deactivated, for example, In an example, if the C_i field is set to zero. An R field may indicate a reserved bit. The R field may be set to zero.

A base station may send (e.g., transmit) DCI via a PDCCH for at least one of: a scheduling assignment and/or grant; a slot format notification; a pre-emption indication; and/or a power-control command. The DCI may comprise at least one of: an identifier of a DCI format; a downlink scheduling assignment(s); an uplink scheduling grant(s); a slot format indicator; a pre-emption indication; a power-control for PUCCH/PUSCH; and/or a power-control for SRS.

A downlink scheduling assignment DCI may comprise parameters indicating at least one of: an identifier of a DCI format; a PDSCH resource indication; a transport format; HARQ information; control information related to multiple antenna schemes; and/or a command for power control of the PUCCH. An uplink scheduling grant DCI may comprise parameters indicating at least one of: an identifier of a DCI format; a PUSCH resource indication; a transport format; HARQ related information; and/or a power control command of the PUSCH.

Different types of control information may correspond to different DCI message sizes. Supporting multiple beams, spatial multiplexing in the spatial domain, and/or noncontiguous allocation of RB s in the frequency domain, may require a larger scheduling message, in comparison with an uplink grant allowing for frequency-contiguous allocation. DCI may be categorized into different DCI formats. A DCI format may correspond to a certain message size and/or usage.

A wireless device may monitor (e.g., in common search space or wireless device-specific search space) one or more PDCCH for detecting one or more DCI with one or more DCI format. A wireless device may monitor a PDCCH with a limited set of DCI formats, for example, which may reduce power consumption. The more DCI formats that are to be detected, the more power may be consumed by the wireless device.

The information in the DCI formats for downlink scheduling may comprise at least one of: an identifier of a DCI format; a carrier indicator; an RB allocation; a time resource allocation; a bandwidth part indicator; a HARQ process number; one or more MCS; one or more NDI; one or more RV; MIMO related information; a downlink assignment index (DAI); a TPC for PUCCH; an SRS request; and/or padding (e.g., if necessary). The MIMO related information may comprise at least one of: a PMI; precoding information; a transport block swap flag; a power offset between PDSCH and a reference signal; a reference-signal scrambling sequence; a number of layers; antenna ports for the transmission; and/or a transmission configuration indication (TCI).

The information in the DCI formats used for uplink scheduling may comprise at least one of: an identifier of a DCI format; a carrier indicator; a bandwidth part indication; a resource allocation type; an RB allocation; a time resource allocation; an MCS; an NDI; a phase rotation of the uplink DMRS; precoding information; a CSI request; an SRS request; an uplink index/DAI; a TPC for PUSCH; and/or padding (e.g., if necessary).

A base station may perform cyclic redundancy check (CRC) scrambling for a DCI, for example, before transmitting the DCI via a PDCCH. The base station may perform CRC scrambling by binarily adding multiple bits of at least one wireless device identifier (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SP CSI C-RNTI, and/or TPC-SRS-RNTI) on the CRC bits of the DCI. The wireless device may check the CRC bits of the DCI, for example, if detecting the DCI. The wireless device may receive the DCI, for example, if the CRC is scrambled by a sequence of bits that is the same as the at least one wireless device identifier.

A base station may send (e.g., transmit) one or more PDCCH in different CORESETs, for example, to support a wide bandwidth operation. A base station may transmit one or more RRC messages comprising configuration parameters of one or more CORESETs. A CORESET may comprise at least one of: a first OFDM symbol; a number of consecutive OFDM symbols; a set of resource blocks; and/or a control channel element (CCE) to resource element group (REG) (CCE-to-REG) mapping. A base station may send (e.g., transmit) a PDCCH in a dedicated CORESET for particular purpose, for example, for beam failure recovery confirmation. A wireless device may monitor a PDCCH for detecting DCI in one or more configured CORESETs, for example, to reduce the power consumption.

A base station and/or a wireless device may have multiple antennas, for example, to support a transmission with high data rate (such as in an NR system). A wireless device may perform one or more beam management procedures, as shown in FIG. 9B, for example, if configured with multiple antennas.

A wireless device may perform a downlink beam management based on one or more CSI-RSs and/or one or more SS blocks. In a beam management procedure, a wireless device may measure a channel quality of a beam pair link. The beam pair link may comprise a transmitting beam from a base station and a receiving beam at the wireless device. A wireless device may measure the multiple beam pair links between the base station and the wireless device, for example, if the wireless device is configured with multiple beams associated with multiple CSI-RSs and/or SS blocks.

A wireless device may send (e.g., transmit) one or more beam management reports to a base station. The wireless device may indicate one or more beam pair quality parameters, for example, in a beam management report. The one or more beam pair quality parameters may comprise at least one or more beam identifications; RSRP; and/or PMI, CQI, and/or RI of at least a subset of configured multiple beams.

A base station and/or a wireless device may perform a downlink beam management procedure on one or multiple Transmission and Receiving Point (TRPs), such as shown in FIG. 9B. Based on a wireless device's beam management report, a base station may send (e.g., transmit), to the wireless device, a signal indicating that a new beam pair link is a serving beam. The base station may transmit PDCCH and/or PDSCH to the wireless device using the serving beam.

A wireless device and/or a base station may trigger a beam failure recovery mechanism. A wireless device may trigger a beam failure recovery request (BFRQ) procedure, for example, if at least a beam failure occurs. A beam failure may occur if a quality of beam pair link(s) of at least one PDCCH falls below a threshold. The threshold comprise be an RSRP value (e.g., −140 dbm, −110 dbm, or any other value) and/or a SINR value (e.g., −3 dB, −1 dB, or any other value), which may be configured in a RRC message.

FIG. 20A shows an example of a first beam failure event. A base station 2002 may send (e.g., transmit) a PDCCH from a transmission (Tx) beam to a receiving (Rx) beam of a wireless device 2001 from a TRP. The base station 2002 and the wireless device 2001 may start a beam failure recovery procedure on the TRP, for example, if the PDCCH on the beam pair link (e.g., between the Tx beam of the base station 2002 and the Rx beam of the wireless device 2001) have a lower-than-threshold RSRP and/or SINR value due to the beam pair link being blocked (e.g., by a moving vehicle 2003, a building, or any other obstruction).

FIG. 20B shows an example of a second beam failure event. A base station may send (e.g., transmit) a PDCCH from a beam to a wireless device 2011 from a first TRP 2014. The base station and the wireless device 2011 may start a beam failure recovery procedure on a new beam on a second TRP 2012, for example, if the PDCCH on the beam is blocked (e.g., by a moving vehicle 2013, building, or any other obstruction).

A wireless device may measure a quality of beam pair links using one or more RSs. The one or more RSs may comprise one or more SS blocks and/or one or more CSI-RS resources. A CSI-RS resource may be determined by a CSI-RS resource index (CRI). A quality of beam pair links may be indicated by, for example, an RSRP value, a reference signal received quality (e.g., RSRQ) value, and/or a CSI (e.g., SINR) value measured on RS resources. A base station may indicate whether an RS resource, used for measuring beam pair link quality, is QCLed (Quasi-Co-Located) with DM-RSs of a PDCCH. The RS resource and the DM-RSs of the PDCCH may be QCLed, for example, if the channel characteristics from a transmission on an RS to a wireless device, and that from a transmission on a PDCCH to the wireless device, are similar or same under a configured criterion. The RS resource and the DM-RSs of the PDCCH may be QCLed, for example, if Doppler shift and/or Doppler shift of the channel from a transmission on an RS to a wireless device, and that from a transmission on a PDCCH to the wireless device, are the same.

A wireless device may monitor a PDCCH on M beams (e.g. 2, 4, 8) pair links simultaneously, where M≥1 and the value of M may depend at least on capability of the wireless device. Monitoring a PDCCH may comprise detecting DCI via the PDCCH transmitted on common search spaces and/or wireless device specific search spaces. Monitoring multiple beam pair links may increase robustness against beam pair link blocking. A base station may send (e.g., transmit) one or more messages comprising parameters indicating a wireless device to monitor PDCCH on different beam pair link(s) in different OFDM symbols.

A base station may send (e.g., transmit) one or more RRC messages and/or MAC CEs comprising parameters indicating Rx beam setting of a wireless device for monitoring PDCCH on multiple beam pair links. A base station may send (e.g., transmit) an indication of a spatial QCL between DL RS antenna port(s) and DL RS antenna port(s) for demodulation of DL control channel. The indication may comprise a parameter in a MAC CE, an RRC message, DCI, and/or any combinations of these signaling.

A base station may indicate spatial QCL parameters between DL RS antenna port(s) and DM-RS antenna port(s) of DL data channel, for example, for reception of data packet on a PDSCH. A base station may send (e.g., transmit) DCI comprising parameters indicating the RS antenna port(s) are QCLed with DM-RS antenna port(s).

A wireless device may measure a beam pair link quality based on CSI-RSs QCLed with DM-RS for PDCCH, for example, if a base station sends (e.g., transmits) a signal indicating QCL parameters between CSI-RS and DM-RS for PDCCH. The wireless device may start a BFR procedure, for example, if multiple contiguous beam failures occur.

A wireless device may send (e.g., transmit) a BFRQ signal on an uplink physical channel to a base station, for example, if starting a BFR procedure. The base station may send (e.g., transmit) DCI via a PDCCH in a CORESET, for example, after or in response to receiving the BFRQ signal on the uplink physical channel. The wireless may determine that the BFR procedure is successfully completed, for example, after or in response to receiving the DCI via the PDCCH in the CORESET.

A base station may send (e.g., transmit) one or more messages comprising configuration parameters of an uplink physical channel, or signal, for transmitting a beam failure recovery request. The uplink physical channel or signal may be based on one of: a contention-free PRACH (BFR-PRACH), which may be a resource orthogonal to resources of other PRACH transmissions; a PUCCH (e.g., BFR-PUCCH); and/or a contention-based PRACH resource (e.g., CF-PRACH). Combinations of these candidate signals and/or channels may be configured by the base station. A wireless device may autonomously select a first resource for transmitting the BFRQ signal, for example, if the wireless device is configured with multiple resources for a BFRQ signal. The wireless device may select a BFR-PRACH resource for transmitting a BFRQ signal, for example, if the wireless device is configured with the BFR-PRACH resource, a BFR-PUCCH resource, and/or a CF-PRACH resource. The base station may send (e.g., transmit) a message to the wireless device indicating a resource for transmitting the BFRQ signal, for example, if the wireless device is configured with a BFR-PRACH resource, a BFR-PUCCH resource, and/or a CF-PRACH resource.

A base station may send (e.g., transmit) a response to a wireless device, for example, after receiving one or more BFRQ signals. The response may comprise the CRI associated with the candidate beam that the wireless device may indicate in the one or multiple BFRQ signals. A base station and/or a wireless device may perform one or more beam management procedures, for example, if the base station and/or the wireless device are configured with multiple beams (e.g., in system such as in an NR system). The wireless device may perform a beam failure recovery (BFR) procedure (e.g., send one or more BFRQ signals), for example, if one or more beam pair links between the base station and the wireless device fail.

FIG. 21 shows an example BFR procedure. At step 2101, a wireless device may receive one or more messages (e.g., RRC messages) comprising one or more BFR parameters. Although described in connection with a single beam failure, BFR procedures such as the procedure of FIG. 21 may be performed in connection with multiple (e.g., simultaneous) beam failures. At step 2102, the wireless device may detect a beam failure according to one or more BFR parameters, for example, at least one of the BFR parameters received at step 2101. The wireless device may start a first timer, for example, after or in response to detecting the beam failure. At step 2103, the wireless device may select a selected beam, for example, a beam, from a set of candidate beams, with good channel quality (e.g., based on one or more of RSRP, SINR, or BLER). The candidate beams may be identified by a set of reference signals (e.g., SSBs and/or CSI-RSs). The wireless device may select the selected beam, for example, after or in response to detecting the beam failure. At step 2104, the wireless device may send (e.g., transmit) one or more BFR signals to a base station (e.g., a gNB), for example, after or in response to the selecting the selected beam. The one or more BFR signals may be associated with the selected beam. The wireless device may transmit the one or more BFR signals with a transmission beam corresponding to a receiving beam associated with the selected beam. The one or more BFR signals may comprise, for example, one or more of: a preamble transmitted on a PRACH resource, a SR signal transmitted on a PUCCH resource, a beam failure recovery signal transmitted on a PUCCH resource, or a beam report transmitted on a PUCCH/PUSCH resource. The wireless device may start a response window, for example, after or in response to transmitting the one or more BFR signals. The response window may be a timer with a value configured (or determined) by the base station. At step 2105, the wireless device may monitor a PDCCH in a first CORESET. The wireless device may monitor the PDCCH in the first CORESET, for example, if the response window is running. The first CORESET may be associated with the BFR procedure. The wireless device may monitor the PDCCH in the first CORESET, for example, in condition of sending (e.g., transmitting) the one or more BFR signals. At step 2106, the wireless device may receive first DCI via the PDCCH in the first CORESET, for example, during the response window (e.g., if the response window is running). At step 2017, the wireless device may determine that the BFR procedure is successfully completed, for example, after or in response to receiving the first DCI via the PDCCH in the first CORESET. The wireless device may stop the timer and/or stop the response window, for example, after or in response to the BFR procedure successfully being completed.

At step 2106, if the wireless device does not receive the DCI (e.g., before the response window expires), the wireless device may increment a transmission number. The transmission number may be initialized to a first number (e.g., 0) before the BFR procedure is triggered. At step 2108, the wireless device may determine if the transmission number satisfies (e.g., indicates a number less than) a predetermined value (e.g., a configured maximum transmission number). If the transmission number satisfies the predetermined value, the wireless device may repeat one or more of steps 2104, 2105, 2106, or 2108 by, e.g., performing actions comprising at least one of: sending (e.g., transmitting) a BFR signal, starting a response window (e.g., a timer), monitoring the PDCCH, determining if DCI is received, or incrementing the transmission number if no DCI is received (e.g., during the response window and/or while the timer is running). If at step 2108 the transmission number does not satisfy the predetermined value (e.g., if the transmission number indicates a number equal or greater than the predetermined value), the wireless device may at step 2109 declare that the BFR procedure is unsuccessfully completed.

A MAC entity of a wireless device may be configured (e.g., by an RRC layer) with a BFR procedure. The BFR procedure may be used for indicating, to a serving base station, a new SSB and/or a new CSI-RS if a beam failure is detected on one or more serving SSBs and/or CSI-RSs of the serving base station. The beam failure may be detected, for example, by counting at least one beam failure instance indication from a lower layer of the wireless device (e.g., a PHY layer) to the MAC entity.

An RRC layer may configure a wireless device with one or more of the following parameters in a BeamFailureRecoveryConfig for a beam failure detection procedure and/or a BFR procedure: beamFailurelnstanceMaxCount for a beam failure detection, beamFailureDetectionTimer for the beam failure detection, beamFailureCandidateBeamThreshold (e.g., an RSRP threshold for a beam failure recovery), preamblePowerRampingStep for the BFR, preambleReceivedTargetPower for the BFR, preambleTxMax for the BFR, or an ra-ResponseWindow. The ra-ResponseWindow may be a time window to monitor one or more responses for the BFR using a contention-free Random Access preamble.

A wireless device may, for example, use at least one variable (e.g., a UE variable) for a beam failure detection. A BFI_COUNTER may be one of the at least one variables used. The BFI_COUNTER may be a counter for beam failure instance indication. The BFI_COUNTER may be initially set to zero.

If a MAC entity of a wireless device receives a beam failure instance indication from a lower layer of the wireless device, the wireless device may start or restart beamFailureDetectionTimer. The wireless device may also (e.g., in conjunction with starting beamFailureDetectionTimer) or alternatively increment BFI_COUNTER by one. The wireless device may initiate a Random Access procedure on an SpCell based on the BFI_COUNTER being equal to beamFailurelnstanceMaxCount+1. The wireless device may apply the parameters in the BeamFailureRecoveryConfig based on initiating the Random Access procedure. If the beamFailureDetectionTimer expires, the wireless device may set the BFI_COUNTER to zero. If the Random Access procedure is successfully completed, the wireless device may consider the beam failure recovery procedure successfully completed.

If a MAC entity of a wireless device sends (e.g., transmits) a contention-free random access preamble for a BFRQ, the MAC entity may start an ra-ResponseWindow at a PDCCH, for example, a first PDCCH occasion following the end of the transmitting the contention-free random access preamble. The ra-ResponseWindow may be configured in BeamFailureRecoveryConfig. The wireless device may, for example, if the ra-ResponseWindow is running, monitor at least one PDCCH of an SpCell for a response to the BFRQ. The BFRQ may be identified by a C-RNTI. If a notification of a reception of a PDCCH transmission is received from a lower layer of the wireless device, if the PDCCH transmission is addressed to a C-RNTI, and if a contention-free random access preamble for a BFRQ was sent (e.g., transmitted) by a MAC entity of the wireless device, the wireless device may consider the random access procedure successfully completed.

A wireless device may initiate a contention-based random access preamble for a BFRQ. A MAC entity of the wireless device may start a ra-ContentionResolutionTimer if, for example, the wireless device transmits Msg3. The ra-ContentionResolutionTimer may be configured by the RRC layer. The wireless device may, for example, based on starting the ra-ContentionResolutionTimer, monitor at least one PDCCH if the ra-ContentionResolutionTimer is running. The wireless device may consider the random access procedure successfully completed, for example, if a notification of a reception of a PDCCH transmission is received from a lower layer of the wireless device, if a C-RNTI MAC-CE is included in the Msg3, and/or if a random access procedure was initiated for a BFR procedure and the PDCCH transmission is addressed to a C-RNTI of the wireless device. The wireless device may, for example, based on the random access procedure being successfully completed, stop the ra-ContentionResolutionTimer. If a random access procedure of a BFR procedure is successfully completed, the wireless device may consider the BFR procedure successfully completed.

A wireless device may be configured (e.g., for a serving cell) with a first set of periodic CSI-RS resource configuration indexes by a higher layer parameter Beam-Failure-Detection-RS-ResourceConfig. The wireless device may also or alternatively be configured with a second set of CSI-RS resource configuration indexes and/or SS/PBCH block indexes by a higher layer parameter Candidate-Beam-RS-List. The first set and/or the second set may be used for radio link quality measurements on the serving cell. The wireless device may determine, for example, if the wireless device is not provided with a higher layer parameter Beam-Failure-Detection-RS-ResourceConfig, a first set to include SS/PBCH block indexes and periodic CSI-RS resource configuration indexes. The SS/PBCH block indexes and the periodic CSI-RS resource configuration indexes may comprise values that are the same as one or more RS indexes in one or more RS sets. The one or more RS indexes in the one or more RS sets may be indicated, for example, by one or more TCI states. The one or more TCI states may, for example, be used for respective CORESETs with which the wireless device is configured for monitoring PDCCH. The wireless device may, for example, expect a single port RS in the first set.

A first threshold (e.g., Qout,LR) may, for example, correspond to a first default value of a higher layer parameter RLM-IS-OOS-thresholdConfig. A second threshold (e.g., Qin,LR) may, for example, correspond to a second default value of a higher layer parameter Beam-failure-candidate-beam-threshold. A physical layer in the wireless device may assess a first radio link quality according to the first set of periodic CSI-RS resource configurations against the first threshold. For the first set, the wireless device may assess the first radio link quality according to periodic CSI-RS resource configurations and/or SS/PBCH blocks. The periodic CSI-RS resource configurations and/or the SS/PBCH blocks may, for example, be associated (e.g., quasi co-located) with at least one DM-RS of a PDCCH monitored by the wireless device.

A wireless device may, for example, apply the second threshold to a first layer-1 reference signal received power (L1-RSRP) for SS/PBCH blocks. The wireless device may apply the second threshold to a second L1-RSRP for periodic CSI-RS resources based on, for example, after, scaling a respective CSI-RS reception power with a value provided by a higher layer parameter Pc_SS.

A physical layer in a wireless device may, for example, in slots where the first radio link quality according to the first set is assessed, provide an indication to higher layers (e.g., the MAC layer). The wireless device may provide an indication to higher layers if the first radio link quality for all corresponding resource configurations in the first set is worse than the first threshold. The wireless device may use the corresponding resource configurations in the first set to assess the first radio link quality. The physical layer may inform the higher layers (e.g. the MAC layer and/or the RRC layer) when the first radio link quality is worse than the first threshold with a first periodicity. The first periodicity may be determined, for example, by a maximum between the shortest periodicity of periodic CSI-RS configurations or SS/PBCH blocks in the first set and a predetermined value (e.g., 10 ms).

A wireless device may, for example, based on a request from higher layers (e.g., the MAC layer), provide to the higher layers the periodic CSI-RS configuration indexes and/or SS/PBCH block indexes from the second set. The wireless device may also or alternatively provide, to the higher layers, corresponding L1-RSRP measurements that are larger than or equal to the second threshold.

A wireless device may be configured with a CORESET by a higher layer parameter Beam-failure-Recovery-Response-CORESET. The wireless device may also or alternatively be configured with an associated search space provided by a higher layer parameter search-space-config. The associated search space may be used for monitoring a PDCCH in the CORESET. The wireless device may receive from higher layers (e.g., the MAC layer), by a parameter Beam-failure-recovery-request-RACH-Resource, a configuration for a PRACH transmission. For the PRACH transmission in slot n and based on antenna port quasi co-location parameters associated with periodic CSI-RS configuration and/or SS/PBCH block with a first RS index, the wireless device may monitor the PDCCH for detection of a DCI format starting from slot n+4 within a window. The window may be configured by a higher layer parameter Beam-failure-recovery-request-window. The DCI format may comprise a CRC scrambled by a C-RNTI. For a PDSCH reception, the wireless device may assume the antenna port quasi-collocation parameters (e.g., as for monitoring the PDCCH) until the wireless device receives, for example, via higher layers, an activation for a TCI state and/or a parameter TCI-StatesPDCCH.

A base station may control one or more time resources and/or one or more frequency resources that may be used by a wireless device to report CSI. The CSI may comprise a CQI, a precoding matrix indicator PMI, a CSI-RS resource indicator (CRI), a layer indication (LI), a rank indication (RI), and/or and an L1-RSRP.

For CQI, PMI, CRI, LI, RI, L1-RSRP, a wireless device may, for example, be configured by higher layers with one or more CSI-ReportConfig Reporting Settings, one or more CSI-ResourceConfig Resource Settings, and/or a list of trigger states ReportTriggerList. The list of trigger states may contain a list of associated CSI-ReportConfigs indicating the Resource Set IDs for channel and/or for interference.

Each reporting setting CSI-ReportConfig may, for example, be associated with a single downlink BWP (e.g., indicated by a higher layer parameter bandwidthPartId). Each reporting setting may also or alternatively contain one or more reported parameters for one CSI reporting band (e.g., CSI Type (I or II) (if reported), codebook configuration (e.g., comprising codebook subset restriction), time-domain behavior, frequency granularity for CQI and/or PMI, measurement restriction configurations, the layer indicator (LI), the reported L1-RSRP parameter(s), CRI, and/or SSBRI (SSB Resource Indicator)).

A time domain behavior of the CSI-ReportConfig may, for example, be indicated by a higher layer parameter reportConfigType. The time domain behavior may be set to aperiodic, semi-persistent, or periodic CSI reporting. For periodic and semi-persistent CSI reporting, a configured periodicity and a slot offset may apply in a numerology of an UL BWP. The wireless device may send (e.g., transmit) the CSI report on the UL BWP. The higher layer parameter ReportQuantity may indicate CS I-related or L1-RSRP-related quantities to report. The parameter ReportFreqConfiguration may indicate the reporting granularity in the frequency domain, for example, the CSI reporting band and/or whether PMI/CQI reporting is wideband or sub-band. The CSI-ReportConfig parameter may comprise timeRestrictionForChannelMeasurements enabling the configuration of time domain restriction for channel measurements and timeRestrictionForInterferenceMeasurements enabling the configuration of time domain restriction for interference measurements. The CSI-ReportConfig parameter may comprise CodebookConfig, which may comprise configuration parameters for Type-I or Type II CSI (e.g., codebook subset restriction), and configurations of group based reporting.

Each CSI Resource Setting CSI-ResourceConfig may comprise a configuration of one or more CSI Resource Sets. Each of the one or more CSI Resource Sets may comprise CSI-RS resources (e.g., comprised of either NZP CSI-RS or CSI-IM) and/or SS/PBCH Block resources used for L1-RSRP computation. The CSI Resource Setting may be located in the DL BWP identified by the higher layer parameter bwp-id. CSI Resource Settings, for example, all CSI Resource Settings linked to a CSI Report Setting, may have the same DL BWP.

For an L1-RSRP computation, a wireless device may, for example, be configured with one or more CSI-RS resources and/or one or more SS/PBCH Block resources. For an L1-RSRP computation, a wireless device may, for example, be configured with a CSI-RS resource setting. The CSI-RS resource setting may, for example, comprise as many as sixteen CSI-RS resource sets. Each of the sixteen CSI-RS resource sets may, for example, comprise as many as 64 resources. A total number of different CSI-RS resources over all resource sets may, for example, comprise and/or be limited to 128 or fewer CSI-RS resources.

For a L1-RSRP reporting, if a higher layer parameter nrofReportedRS is configured to be one, a reported L1-RSRP value may be defined by a 7-bit value. The reported L1-RSRP value may be in the range [−140, −44] dBm with 1 dB step size. For an L1-RSRP reporting, if a higher layer parameter nrofReportedRS is configured to be larger than one, or if the higher layer parameter group-based-beam-reporting is configured as ‘ON’, the wireless device may use differential L1-RSRP based reporting, where a largest L1-RSRP value may use a 7-bit value in the range [−140, −44] dBm with 1 dB step size, and the differential L1-RSRP may use a 4-bit value. The differential L1-RSRP value may be computed with 2 dB step size with a reference to the largest L1-RSRP value which may be part of the same L1-RSRP reporting instance.

A base station may transmit, to a wireless device, one or more messages comprising configuration parameters of one or more cells. The one or more cells may comprise at least one PCell/PSCell and one or more SCells. An SpCell (e.g., a PCell or a PSCell) and one or more SCells may, for example, operate on different frequencies and/or different bands. An SCell may support a multi-beam operation in which a wireless device may perform one or more beam management procedures (e.g., a BFR procedure) on the SCell. The wireless device may perform a BFR procedure, for example, if at least one of one or more beam pair links associated with the SCell and with the wireless device fails. Existing BFR procedures may result in inefficiencies if there is a beam failure for one of the one or more SCells. Existing BFR procedures may be inefficient, take a relatively long time to complete, and/or increase battery power consumption if used for an SCell.

For PCells, a BFR procedure may mimic and/or reuse a random-access procedure. If a PCell random-access procedure is unsuccessfully completed, a wireless device may declare a radio link failure (RLF). Based on declaring the RLF, the wireless device may try to re-establish a connection with the base station (e.g., using a procedure similar to that used when a wireless device is powered ON). A random-access procedure for an SCell may be initiated by a base station (e.g., via a PDCCH order). If an SCell random-access procedure is under the control of the base station (e.g., if the wireless device does not autonomously initiate the random-access procedure) and is unsuccessfully completed, the base station may be aware of the unsuccessful completion and, based on being aware of that unsuccessful completion, able to take additional action.

Application of PCell BFR procedures to SCell BFR may cause problems and/or may be impractical if, for example, a wireless device determines an SCell beam failure and/or initiates a BFR procedure autonomously. If a wireless device autonomously initiates a random-access procedure as part of an SCell BFR procedure, the base station may be unaware if the BFR procedure unsuccessfully completes. The wireless device may be unable to declare an RLF for the SCell to indicate to the base station that a BFR procedure for the SCell has unsuccessfully completed.

Problems may occur if a base station is unaware that a BFR procedure for an SCell has unsuccessfully completed. The base station may, for example, continue sending uplink and/or downlink scheduling information for that SCell to a wireless device. Because of the beam failure on that SCell, the wireless device may be unable to receive that scheduling information. Signaling overhead may be unnecessarily increased. Time and/or frequency resources allocated to that SCell may be wasted, as the wireless device may be unable to use those resources (e.g., because it cannot receive the scheduling information). If a base station is aware that a BFR procedure for an SCell has unsuccessfully completed, the base station may be able to take appropriate action (e.g., deactivating the SCell, stop scheduling for the SCell, and/or initiate an aperiodic beam management to determine a suitable beam to serve the SCell) to mitigate some or all of these problems.

Unsuccessful completion of a BFR procedure for the SCell may indicate that candidate beams for that SCell are insufficient. If that BFR procedure comprises a random access procedure initiated by the wireless device, and if the wireless device is unable to declare an RLF if that random access procedure fails, the base station may be unaware of the unsuccessful BFR procedure. The base station may be unable, for example, based on being unaware of the unsuccessful BFR procedure, to instruct the wireless device to discontinue monitoring of downlink signals in the SCell. The base station may similarly be unable to instruct the wireless device to discontinue uplink transmissions in the SCell. If a wireless device continues to monitor downlink control channels for an SCell after an unsuccessful BFR procedure, the wireless device may unnecessarily consume power attempting to receive signals when no sufficient beams are available. If the wireless device continues performing uplink transmissions, the wireless device may unnecessarily increase uplink interference (e.g., decrease signal quality) for other cells and/or other wireless devices. If downlink beams are insufficient, for example, transmitting uplink signals via the SCell may be useless if the wireless device is not able to receive acknowledgment (ACK) of such uplink signals.

An SCell may be configured for a wireless device with a deactivation timer controlling activation status of the SCell (e.g., by deactivating the SCell if DCI indicating an uplink grant (for an uplink data transmission) or a downlink assignment (for a downlink data transmission) is not received before the timer expiration). If a deactivation timer is used for an SCell, and a wireless device takes no other action if a BFR procedure for that SCell unsuccessfully completes, the SCell may be deactivated based on expiration of the timer. An SCell deactivation timer may have a relatively long duration (e.g., 1024 ms), and the above described problems (e.g., interference, power consumption) may continue if the timer is unexpired and a BFR procedure has not succeeded. Shortening the duration of an SCell deactivation timer may cause other problems. If duration of an SCell deactivation timer is reduced, the SCell may be deactivated frequently. Reactivating a deactivated SCell may require additional activation signaling from the base station, and/or the wireless device may need to perform channel measurements based on receiving the additional activation signaling. The additional activation signaling and/or channel measurements may increase signaling overhead between the base station and the wireless device, and may also increase the latency for SCell activation.

A base station may configure an SCell for a wireless device for periodic beam reporting. A wireless device may, for example, be configured to measure RSRP of M RSs of the SCell (where M may be an integer value), and to report the N RSs with highest RSRP values (where N may be equal to or less than M) based on a period T (e.g., the wireless device may be configured to transmit the beam report at times T, 2T, 3T, etc.). The wireless device may send the periodic reporting via one or more PUCCHs. Values for RSRP (e.g., in dBm) may be mapped to 7-bit values (e.g., in a mapping table stored by a wireless device and by a base station), as described below in connection with FIG. 25 . Some 7-bit values may be reserved and not used for reporting of RSRP values (and/or not used for other types of values associated with beam reporting). One or more reserved values may be used to indicate unsuccessful completion of an SCell BFR procedure, as described below. The wireless device may include the one or more reserved values, for example, in beam reporting that the wireless device sends to a PCell and/or to another cell different from the SCell for which a beam failure was determined. The base station may determine, based on the one or more reserved values sent by the wireless device, that a BFR procedure has unsuccessfully completed for the SCell where the beam failure was determined. The base station may, based on determining that unsuccessful completion, take appropriate action (e.g., deactivate the SCell for the wireless device, discontinue sending of uplink and/or downlink scheduling information to the wireless device for that SCell, reallocate time and/or frequency resources). Based on determining unsuccessful completion of a BFR procedure for the SCell, the wireless device may, for example, without waiting for expiration of a deactivation timer for that SCell, discontinue monitoring downlink control channels for that SCell and/or may take other action. Radio efficiency may be improved, signaling overhead may be reduced, spurious and/or unnecessary uplink and/or downlink transmissions may be reduced, and/or consumption of the wireless device's battery power may be reduced.

If a wireless device is configured with an SCell comprising downlink-only resources, a wireless device may be unable to send (e.g., transmit) an uplink signal (e.g., a preamble) in that SCell for a BFR procedure if a beam failure occurs on the SCell. The wireless device may be unable to perform a BFR procedure on that SCell, and a base station may not become aware of the beam failure on that SCell. Including a value (e.g., a reserved value, as described above) in signaling sent by the wireless device to a PCell (and/or another cell different from the SCell) may be used to inform the base station of the beam failure.

An SCell may, for example, operate in a higher frequency band (e.g. 23 GHz, 60 GHz, 70 GHz). An SpCell may, for example, operate in a lower frequency band (e.g. 2.4 GHz, 5 GHz). The channel condition of the SCell may be different from the channel condition of the SpCell. The wireless device may use uplink resources of the SpCell to send (e.g., transmit) a preamble for a beam failure recovery request for the SCell, to improve robustness of transmission of the preamble. BFR procedures may be enhanced for an SCell operating in a different frequency band than an SpCell. That SCell (e.g., an SCell for which an uplink control channel is not configured) may be configured to send beam reporting via uplink control channels of that SpCell (e.g., a PCell). Even if there is a beam failure in the SCell, there may no problem with the SpCell, and indicating unsuccessful completion of a BFR for the SCell, via the periodic beam reporting on the SpCell, may be reliable and robust.

A wireless device may be configured with a BFR timer that may be used, for example, to limit a duration of a BFR procedure. The wireless device may be configured with an SCell deactivation timer that is used, for example, to cause deactivation of the SCell (e.g., if no DCI has been received). The duration of the SCell deactivation timer (e.g., 1280 ms) may be greater than that of the BFR timer (e.g., 200 ms). If a BFR procedure of an SCell fails, for example due to an expiry of the BFR timer, the wireless device may continue to perform uplink transmissions and/or monitor downlink transmissions via the SCell until the SCell deactivation timer expires. A time gap between the expiry of the BFR timer and an expiry of the SCell deactivation timer may be relatively large (e.g., approximately 1000 ms). During the time gap, the wireless device may cause uplink interference to other users/cells. During the time gap, the wireless device may, for example, miss one or more DCI transmitted by the base station on at least one PDCCH of the SCell. This may result in a high power consumption of the wireless device and/or signaling overhead of the base station.

Additional operations of a wireless device, during a time gap between the expiry of the BFR timer and an expiry of the SCell deactivation timer, may cause inefficiencies and/or other problems. A wireless device may, for example, use a DL SCell as a pathloss reference for an UL transmission and may observe a poor radio link quality (e.g., higher than % 10 BLER) on the DL SCell. The poor radio link quality may, for example, be caused by a beam failure. The beam failure may be associated with one or more downlink control channels of the DL SCell. If the wireless device continues to use the DL SCell with the poor radio link quality as the pathloss reference for the UL transmission, the wireless device may generate unnecessary interference due to spurious uplink transmissions. A wireless device may be out of synchronization, for example based on a beam failure, on a DL SCell. The wireless device may generate spurious uplink transmissions based on being out of synchronization in the downlink channel, and the spurious uplink transmissions may generate interference to other users/cells. A base station may send (e.g., transmit), to a wireless device, transmit power control commands for an uplink transmission of an SCell. If there is a beam failure for that SCell, the wireless device may not receive the transmit power control commands on one or more downlink control channels of that SCell, and/or the transmit power control commands received by the wireless device may be unreliable. Based on unreceived or unreliable transmit power control commands, the wireless device may fail to properly control power of the uplink transmission of the SCell. This may result in interference to other users/cells.

A wireless device may discontinue, based on expiration of a BFR timer and/or other determination of an unsuccessfully completed BFR procedure, UL transmissions in an SCell associated with a beam failure. The wireless device may discontinue those UL transmissions in the SCell prior to expiration of an SCell deactivation timer that may be configured for the SCell. The wireless device may discontinue those UL transmissions independently of whether a base station is made aware of the unsuccessfully completed BFR procedure. A wireless device may also or alternatively discontinue, based on expiration of the BFR timer and/or other determination of the unsuccessfully completed BFR procedure, monitoring of DL transmissions in that SCell. The wireless device may discontinue monitoring those DL transmissions prior to expiration of the SCell deactivation timer that may be configured for the SCell. The wireless device may discontinue monitoring those DL transmissions independently of whether the base station is made aware of the unsuccessfully completed BFR procedure. By such discontinuing of UL transmissions and/or monitoring of DL transmissions, inefficiencies and other problems (e.g., as described above) may be reduced.

A base station may not detect a beam failure or a failure of a BFR procedure for an SCell using a CQI report and/or a configured radio resource management (RRM) measurement report for the SCell. The CQI report and/or the configured RRM report may, for example, be lost or delayed. A wireless device sending (e.g., transmitting) an alternate and/or additional uplink notification of a failure of a BFR for an SCell to a base station may enable the base station to detect the BFR failure for the SCell more rapidly (e.g., more rapidly than a CQI report and/or an RRM report). The alternate and/or additional uplink notification may comprise including a value (e.g., a reserved value, as described herein) in signaling sent by the wireless device to a PCell (and/or another cell different from the SCell).

As described above, a wireless device may stop uplink transmissions for an SCell based on determining a failure of a BFR procedure for that SCell. Based on stopping the uplink transmissions, the wireless device may transmit an uplink notification of a failure of a BFR procedure for the SCell via uplink resources of a first cell (e.g. PCell).

A wireless device that has stopped uplink transmissions of an SCell, based on a failure of a BFR procedure of that SCell, may autonomously resume the uplink transmissions if a radio quality of at least one downlink channel of the SCell recovers (e.g., before an SCell deactivation timer of that SCell expires). The recovery of the at least one downlink channel of the SCell may comprise, for example, receiving DCI on the at least one downlink channel of the SCell.

A wireless device may, based on a failure of a BFR for an SCell, stop monitoring at least one PDCCH in the one or more CORESETs of the SCell. The one or more CORESETs may comprise a dedicated CORESET and/or a common CORESET. The dedicated CORESET may be used, for example, to receive a response (e.g., DCI) from a base station to complete a BFR procedure. The stopping monitoring the at least one PDCCH may result in a reduced power consumption of the wireless device.

Based on receiving an uplink notification of a failure of a BFR procedure for an SCell, a base station may deactivate and/or release the SCell. The deactivating and/or the releasing of the SCell may be performed via MAC CE signaling. Based on receiving the uplink notification, for example, the base station may stop scheduling the wireless device on the SCell. The stopping of the scheduling on the SCell may avoid waste of resources due to unnecessary scheduling.

Based on a failure of a BFR procedure for an SCell, a wireless device may autonomously deactivate the SCell. Based on deactivating the SCell, the wireless device may send (e.g., transmit) an uplink notification of the failure of the BFR procedure for the SCell via uplink resources of a first cell (e.g. PCell).

An uplink notification of a failure of a BFR procedure for an SCell may be based on beam reporting via a PUCCH, an RRC message, and/or a MAC CE. The uplink notification may comprise an identity of the SCell associated with the beam failure.

A detection of a beam failure instance may, for example, be based on hypothetical PDCCH BLER. Using beam reporting via a PUCCH, a wireless device may report one or more L1-RSRP values associated with one or more first RSs. The one or more first RSs may be associated with one or more second RSs (e.g., one or more DM-RSs) of at least one PDCCH. The base station may be unable to determine, based on values in the PUCCH beam reporting that indicate actual values (e.g., actual L1-RSRP values), a beam failure instance. A wireless device may, for example, assess a low BLER (e.g., higher than % 10 BLER) on the at least one PDCCH, but that at least one PDCCH may have a high L1-RSRP. The base station may not be able to determine, based on the high L1-RSRP reported via the PUCCH, the low BLER on the at least one PDCCH. To notify a base station of a failure of a BFR procedure of an SCell using a PUCCH beam reporting, a wireless device may include a value (e.g., a reserved value) in such reporting that does not indicate an actual value.

FIG. 22 shows an example timeline for an example BFR procedure. The BFR procedure may, for example, be for an SCell and/or may successfully complete. FIG. 23 is a flowchart showing steps of an example BFR procedure. The example timeline of FIG. 22 may, for example, be associated with the example procedure of FIG. 23 . For convenience, FIG. 22 may indicate multiple operations occurring at a single time. Multiple operations associated with a single time of the FIG. 22 timeline need not occur at the same instant or within a specific amount of time, and need not occur in a specific order relative to one another. The order of operations shown in FIG. 22 , and/or of steps shown in FIG. 23 , may be varied. One or more of the operations and/or steps may be modified or omitted, and/or other operations and/or steps may be added.

At step 2301 (FIG. 23 ), and as shown at time T0 (FIG. 22 ), a wireless device 2201 may receive (e.g., from a base station) one or more messages comprising configuration parameters. The wireless device may receive the one or more messages via a first cell 2200 (e.g., a PCell). The one or more messages may comprise one or more RRC messages (e.g. an RRC connection reconfiguration message, an RRC connection reestablishment message, and/or an RRC connection setup message). The configuration parameters may comprise one or more BFR configuration parameters. The one or more BFR configuration parameters may comprise a first set of RS resource configurations for a second cell 2202 (e.g., an SCell). The first set of RS resource configurations may comprise one or more first RSs (e.g., CSI-RS and/or SS blocks) of the second cell 2202. The one or more BFR configuration parameters may comprise a second set of RS resource configurations comprising one or more second RSs (e.g., CSI-RS and/or SS blocks) of the second cell 2202. The wireless device 2201 may measure radio link quality of one or more beams associated with the one or more first RSs and/or the one or more second RSs. The one or more BFR configuration parameters may comprise one or more beam failure recovery request (BFRQ) resources associated with the second cell 2202. The BFRQ resources may, for example, be on the first cell 2200 (e.g., if the second cell 2202 is configured without uplink resources for the wireless device 2201). The BFRQ resources may be on the second cell 2202. The one or more BFR configuration parameters may comprise an association between each of the one or more second RSs and each of the one or more BFRQ resources. The one or more messages received at step 2301, and/or other messages received from the base station, may comprise configuration parameters defining and/or otherwise indicating reporting (e.g., beam reporting as described below) to be performed by the wireless device.

A base station may, for example, if configured with carrier aggregation (CA), send (e.g., transmit), to the wireless device 2201, an SCell Activation/Deactivation MAC CE activating the second cell 2202. At step 2302 (FIG. 23 ), the wireless device 2201 may determine if a MAC CE for second cell activation has been received. If not, and as shown at step 2304, the wireless device 2201 may continue operating on the first cell 2200 (e.g., only on the first cell 2200) and/or on other SCells already activated. If a MAC CE for activation of the second cell 2202 is received (e.g., an SCell Activation/Deactivation MAC CE), and as shown at time T1 (FIG. 22 ), the wireless device 2201 may at step 2305 (FIG. 23 ) activate the second cell 2202. Based on receiving the MAC CE (e.g., an SCell Activation/Deactivation MAC CE) for activation of the second sell 2202, the wireless device 2201 may (e.g., at time T1) start or restart an SCell deactivation timer associated with the second cell 2202.

The wireless device 2201 may, for example, assess a first radio link quality of the one or more first RSs (e.g., First RS 1 and/or First RS 2 in FIG. 22 ) of the second cell 2202 against a first threshold. The first threshold (e.g., a threshold value of hypothetical BLER, a threshold value of L1-RSRP) may be a first value provided by a higher layer (e.g., an RRC layer, a MAC layer). The wireless device 2201 may monitor at least one PDCCH of the second cell 2202. At least one RS (e.g., a DM-RS) of the at least one PDCCH may be associated with (e.g., QCLed) the one or more first RSs. At step 2306 (FIG. 23 ), the wireless device 2201 determine if a BFR procedure is initiated for the second. If not, at step 2307 the wireless device may continue to operate on the first cell 2200 and the second cell 2202.

The wireless device 2201 may detect a beam failure on the second cell 2202 if, for example, a first radio link quality of the one or more first RSs meets one or more predetermined criteria. A beam failure may occur, for example, if RSRP and/or SINR of the one or more first RSs is lower than the first threshold and/or if BLER is higher than the first threshold. The determination of beam failure may be based on evaluations of RSRP, SINR, BLER, and/or other characteristics for a quantity of multiple consecutive RSs. A beam failure may be determined, for example, if all evaluations of the quantity of multiple consecutive RSs meet the one or more predetermined criteria. The quantity of may be provided by a higher layer (e.g., an RRC layer, a MAC layer).

Based on determining a beam failure on the second cell, and as shown at time T2 in FIG. 22 , the wireless device 2201 may initiate a BFR procedure (e.g., a random access procedure) of the second cell 2202. Based on initiating the BFR procedure, the wireless device 2201 may at step 2308 (FIG. 23 ), and as also shown at time T2 (FIG. 22 ), start a BFR timer (if configured) and/or initiate a candidate beam identification procedure. For the candidate beam identification procedure, the wireless device 2201 may identify a first RS (e.g., the Second RS 2) in the one or more second RSs. The first RS may be associated with a BFRQ resource of the one or more BFRQ resources. The BFRQ resource may comprise at least one preamble and at least one PRACH resource (e.g., time and/or frequency). A second radio link quality (e.g., based on BLER and/or L1-RSRP) of the first RS may, for example, be better (e.g., a lower BLER value, a higher L1-RSRP value, and/or a higher SINR value) than a second threshold. The second threshold may, for example, be a second value provided by the higher layer (e.g., the RRC layer, the MAC layer).

Based on detecting the beam failure on the second cell 2202 and on identifying the first RS of the second cell 2202, the wireless device 2201 may at step 2309 initiate a BFRQ transmission. The BFRQ transmission may comprise sending (e.g., transmitting), in a first slot, the at least one preamble via the at least one PRACH resource for the BFR procedure of the second cell. The BFRQ transmission is shown at time T3 of FIG. 22 . The at least one PRACH resource may, for example, be on the first cell 2200 (e.g., if the second cell 2202 is an SCell for which the wireless device 2201 is not configured for uplink transmission). The at least one PRACH resource may be on the second cell 2202 (e.g., if the second cell 2202 is an SCell for which the wireless device 2201 is configured for uplink transmission).

At step 2310, and based on sending (e.g., transmitting) the at least one preamble in the first slot, the wireless device 2201 may start, from a second slot, monitoring for a BFR response. The monitoring for the BFR response may comprise monitoring at least one second PDCCH in one or more CORESETs for first DCI (e.g. a downlink assignment or an uplink grant) within a configured response window. The first DCI may be with CRC scrambled by a C-RNTI of the wireless device 2201.

The one or more CORESETs may, for example, be on the first cell 2200. A wireless device 2201 may monitor the at least second PDCCH of the first cell 2200 in the one or more CORESETs according to an antenna port associated (e.g., QCLed) with at least one third RS. The at least one third RS may, for example, be selected from one or more third RSs of the first cell 2200. At least one fourth RS (e.g., a DM-RS) of the at least second PDCCH may be associated (e.g., QCLed) with the at least one third RS. A base station may transmit an indication of QCL between antenna port(s) of the at least one third RS and the at least one fourth RS.

The one or more CORESETs may be on the second cell. The wireless device 2201 may monitor the at least second PDCCH of the second cell 2202 in the one or more CORESETs according to an antenna port associated (e.g., QCLed) with the first RS selected in the candidate beam identification procedure. At least one fourth RS (e.g., a DM-RS) of the at least second PDCCH may be associated (e.g., QCLed) with the first RS. A base station may transmit an indication of QCL between antenna port(s) of the first RS and the at least one fourth RS.

If BFR response is not received, the wireless device 2201 may at step 2311 determine if a maximum number of BFRQ signal transmissions have been sent for the current BFR procedure, and/or if the BFR timer started at step 2308 has expired. The maximum number or BFRQ transmissions may be configured by a higher layer. If the maximum number of BFRQ signal transmissions have been sent, and/or if the BFR timer has expired, the wireless device 2201 may perform steps 2313 and/or 2314, which are discussed below in connection with FIG. 24 . If the maximum number of BFRQ signal transmissions have not been sent, and/or if the BFR timer has not expired, the wireless device 2201 may repeat step 2309 and send another BFRQ signal.

If a BFR response (e.g., DCI) is received in step 2310, the wireless device 2201 may determine at step 2312 that the BFR procedure is successfully completed. Receipt of a BFR response and successful completion of the BFR procedure are shown at time T4 of FIG. 22 . A determination of successful completion of the BFR procedure may, for example, be based on receiving, within a configured response window, first DCI on the at least one second PDCCH in the one or more CORESETs.

FIG. 24 shows an example timeline for an example BFR procedure. The BFR procedure of FIG. 24 may, for example, be a BFR procedure such as is described in connection with FIGS. 22 and/or 23 , but in which a BFR procedure for the second cell 2202 fails (e.g., unsuccessfully completes). For convenience, FIG. 24 may indicate multiple operations occurring at a single time. Multiple operations associated with a single time of the FIG. 24 timeline need not occur at the same instant or within a specific amount of time, and need not occur in a specific order relative to one another. The order of operations shown in FIG. 24 may be varied. One or more of the operations shown in FIG. 24 may be modified or omitted, and/or other operations may be added.

Operations associated with times T0, T1, T2, and T3 in FIG. 24 may be the same as or similar to the operations described in connection with times T0, T1, T2, and T3 in FIG. 22 , and may be associated with steps of FIG. 23 discussed in connection with times T0, T1, T2, and T3 in FIG. 22 . In the example of FIG. 24 , a maximum number of BFRQ transmission (e.g., preamble transmissions) for the BFR procedure may be sent from time T3 to time T4, and/or the BFR timer may expire at time T4, without the BFR procedure being successfully completed (e.g., without receipt of DCI in response to a sent preamble). At step 2311 (FIG. 23 ), and based on determining that the maximum number of BFRQ transmissions have been sent and/or that the BFR timer has expired without receipt of a response to a BFRQ transmission, and/or based on other determination(s), the wireless device 2201 may at step 2313 determine that the BFR procedure has unsuccessfully completed.

At step 2314, based on determining that the BFR procedure completed unsuccessfully, the wireless device 2201 may indicate a failure of the BFR procedure to a base station. The wireless device may, for example, and as shown at time T5 of FIG. 24 , use periodic PUCCH beam reporting via the first cell 2200 (e.g., a PCell) to send the indication.

A base station may, based on receiving an indication of the failure of a BFR procedure for the second cell 2202, deactivate and/or release the second cell 2202. The deactivating and/or releasing the second cell 2202 may, for example, be performed via MAC CE signaling. Based on receiving the indication, the base station may also or alternatively stop scheduling the wireless device 2201 on the second cell 2202. The stopping of the scheduling on the second cell 2202 may avoid a waste of resources for unnecessary scheduling.

The wireless device 2201 may, based on determining the failure of the BFR for the second cell 2202, stop uplink transmissions for the second cell 2202. The stopping of the uplink transmissions may limit interference to other cells and/or wireless devices. The wireless device 2201 may, based on determining the failure of the BFR for the second cell 2202, stop monitoring at least one PDCCH in the one or more CORESETs of the second cell 2202. The stopping of monitoring the at least one PDCCH may reduce power consumption of the wireless device 2201. The wireless device may, based on determining the failure of the BFR for the second cell 2202, stop uplink transmissions of the second cell 2202. The wireless device 2201 may continue monitoring at least one downlink channel of the second cell 2202 if the second cell 2202 is not deactivated (e.g., based on expiration of a second cell deactivation timer and/or receipt of a MAC CE deactivating the second cell 2202). The wireless device 2201 may autonomously resume the uplink transmissions in the second cell 2202 if a radio quality of the at least one downlink channel of the second cell recovers.

FIG. 25 shows a table of an example mapping of L1-RSRP values to 7-bit values for a periodic PUCCH beam reporting. The table of FIG. 25 may, for example, be stored by a wireless device and/or by a base station. A 7-bit range may accommodate 128 L1-RSRP values or value ranges (e.g., states). Less than 128 7-bit values may be used. To report L1-RSRP values in the range of [−140, −44] dBm, with a 7-bit value assigned to each 1 dB step size, another 7-bit value assigned to indicate all values less than −140 dBm, and another 7-bit value assigned to indicate all values greater than −44 dBm, 98 7-bit values may be used, leaving 30 7-bit values for other uses. One or more values in a range of n-bit values, where n is an integer, may be reserved for a notification of a failure of a beam failure of an SCell. In the example of FIG. 25 , the L1-RSRP values between −140 dBm and −44 dBm may be represented with 7-bit RSRP values between 0000000 and 1100001. One or more of the 7-bit values from 1100010 through 1111111 may be reserved for a notification of an unsuccessful BFR procedure (and/or of a beam failure) of an SCell. For differential RSRP reporting using 4-bit values, one or more of those 4-bit values (e.g., 0000 or 1111) may be used for a notification of an unsuccessful BFR procedure (and/or of a beam failure) of an SCell.

FIGS. 26B through 26D show examples of reporting indicating unsuccessful completion of a BFR procedure and/or a beam failure. Reports used to indicate unsuccessful completion of a BFR procedure and/or to indicate a beam failure may be sent via a physical uplink channel (e.g., a PUCCH) and/or may include indications of measured values of characteristics (e.g., measured values for RSRP and/or L1-RSRP) associated with one or more downlink signals (e.g., one or more RSs). The example reports of FIGS. 26A-26B are shown as tables in which an index field is associated with a value field, and in which an index in that index field is associated with a value in that value field, based adjacency of the index and value fields in a table row. Other formats may be used to report and/or otherwise indicate association of a value (and/or other indicator) with an index, a cell, a beam, a signal, and/or other elements. For example, a wireless device may be configured (e.g., via one or more RRC messages shown at time T0 in FIGS. 22 and 24 ) to send (e.g., via a PUCCH) a series of values, with the order of the values in the series respectively corresponding to indexes associated with the values.

A wireless device may use a PUCCH to provide beam reporting of a cell (e.g., of an SCell). The PUCCH beam reporting may comprise one or more beam indexes and one or more measurement fields. The one or more measurement fields may contain values of a measured characteristic (e.g., L1-RSRP) of one or more signals (e.g., RSs) indicated by indices (e.g., beam indices) associated with the measurement fields. One or more beam indexes may be associated (e.g., QCLed) with one or more RSs of a cell associated with a beam report.

FIG. 26A shows an example beam report 2601 for a second cell (e.g., an SCell) in which the first column (“RS Set”) may comprise N beam index fields, where N may be any integer. Each of the beam index fields may contain an index associated with one of N RSs of the second cell. The indices are for convenience shown in the beam report 2601 as RS 1 through RS N. The second column (“L1-RSRP”) of the beam report 2601 may comprise L1-RSRP measurement fields. In the example of FIG. 26A, each of the L1-RSRP measurement fields comprises a value (e.g., a 7-bit value from the table of FIG. 25 ) mapped to a range of measured values for L1-RSRP. Each of the values of the second column may be associated with the beam index (and may indicate an L1-RSRP value range of the RS associated with that beam index) from the first column that is in the same row. The value of 0001000 may, for example, be associated with the beam index RS 1 and may indicate (e.g., based on the mapping of FIG. 25 ) an L1-RSRP value range for the RS associated with the beam index RS 1. In the example of FIG. 26A, no beam failure or unsuccessful BFR procedure is reported, and each of the L1-RSRP measurement fields may contain a non-reserved 7-bit value (e.g., one of the 7-bit values between 0000000 and 1100001 from the table of FIG. 25 ) mapped to an L1-RSRP value (or to a range of L1-RSRP values). The beam report 2601 may be sent by a wireless device via a PUCCH of the second cell or via a PUCCH of a first cell (e.g., a PCell or another SCell).

FIG. 26B shows an example beam report 2602 for a second cell (e.g., an SCell). The beam report 2602 may, except as described below, be similar to the beam report 2601. In the example of FIG. 26B, the second cell may have unsuccessfully completed a BFR procedure after determining a beam failure of the second cell. A wireless device may send the beam report 2602 to indicate that unsuccessful BFR procedure for the second cell and/or to indicate the beam failure. To indicate the unsuccessful BFR (and/or the beam failure), one or more of the L1-RSRP measurement fields in the beam report 2602 may be populated with a value (e.g., one of the reserved values (e.g., 1111111) from the table of FIG. 25 ) that indicates an unsuccessful BFR procedure and/or a beam failure. A base station that receives the beam report 2602 may determine that a BFR procedure of the second cell was unsuccessful and/or that a beam failure occurred in the second cell. That determination by the base station may be based on the presence in one or more of the L1-RSRP measurement fields of values (e.g., reserved values from FIG. 25 ) indicating an unsuccessful BFR and/or a beam failure, and/or based data (e.g., from a previously-sent RRC and/or other configuration message specifying time and/or frequency resources to send the beam report 2602) indicating that the beam report 2602 is associated with the second cell. The base station may, based on determining an unsuccessful BFR procedure and/or beam failure for the second cell, send a MAC CE to deactivate the second cell and/or may refrain from scheduling the wireless device on the second cell. The beam report 2602 may be sent by a wireless device via a PUCCH of the second cell or via a PUCCH of a first cell (e.g., a PCell or another SCell).

FIG. 26C shows an example beam report 2603 for a cell. The cell for which the report 2603 is sent and/or otherwise associated may be, for example, a second cell (e.g., an SCell). The beam report 2603 may, except as described below, be similar to the beam report 2601. The beam report 2603 may be sent by a wireless device via a PUCCH of the cell associated with the beam report 2603, and/or may be sent via a PUCCH of a another cell (e.g., a PCell or another SCell). In the example of FIG. 26C, the cell associated with the report 2603 may have unsuccessfully completed a BFR procedure after determining a beam failure of that cell. A wireless device may send (e.g., transmit) the beam report 2603 to provide a beam reporting of that cell and that comprises values (e.g., non-reserved values from the table of FIG. 25 ) mapped to measured values of a characteristic (e.g., to L1-RSRP values). The beam report 2603 may comprise an indication of a failure of random access procedure for a BFR for that cell. A first portion of the beam report 2603 (e.g., for the indexes RS 1 through RS N) may be similar to the beam report 2601. A second portion of the beam report 2603 may comprise an additional beam index (e.g., RS N+1) and an additional data field. If there is no beam failure or failure of a BFR procedure for the cell associated with the beam report 2603, the additional data field may be empty or may be populated by the wireless device with a value (e.g., one of the reserved values from FIG. 25 ) indicative of no beam failure and/or of a successful BFR procedure. A base station that receives the beam report 2603 with the additional data field empty (or populated by the value indicative of no beam failure and/or of a successful BFR procedure) may determine that there has been no beam failure for the associated cell and/or that a BFR procedure of the associated cell was successful. That determination by the base station may be based on the empty additional data field (or the presence in that field of the value indicative of no beam failure and/or of a successful BFR procedure), and/or based on data (e.g., from a previously-sent RRC and/or other configuration message specifying time and/or frequency resources to send the beam report 2603) indicating the cell with which the beam report 2603 is associated.

If a BFR procedure for the cell associated with the beam report 2603 was unsuccessful (e.g., a random access procedure for a beam failure recovery for the cell was unsuccessful), the wireless device may populate the additional data field, associated with the additional beam index, with a value (e.g., a different one of the reserved values from FIG. 25 (e.g., 1111111)) indicative of the unsuccessful BFR (and/or of the beam failure). A base station that receives the beam report 2603, with the additional data field populated by the value indicative of a beam failure and/or of an unsuccessful BFR procedure, may determine that a BFR procedure of the associated cell was unsuccessful and/or that a beam failure occurred in the cell. That determination by the base station may be based on the presence in additional data field of the value indicative of the unsuccessful BFR (and/or of the beam failure), and/or based on the data indicating the cell with which the beam report 2603 is associated. The base station may, based on determining that unsuccessful BFR procedure and/or beam failure for the cell, send a MAC CE to deactivate that cell and/or may refrain from scheduling the wireless device on that cell.

A wireless device may send (e.g., transmit) beam reporting (e.g., a PUCCH beam report) of a first cell (e.g., a PCell) to notify a base station of a failure of a BFR procedure for a second cell (e.g., an SCell). That beam reporting may comprise values (e.g., non-reserved values from the table of FIG. 25 ) mapped to measured values of a characteristic (e.g., to L1-RSRP values) for the first cell, and may also comprise one or more indications of one or more unsuccessful BFR procedures (e.g., a failure of random access procedure for a BFR procedure) for one or more second cells.

FIG. 26D shows an example beam report 2604 for a first cell (e.g., a PCell) that reports values for characteristics of the first cell, and that may report an unsuccessful BFR procedure (and/or a beam failure) for one or more second cells. The beam report 2604 may be sent by a wireless device via a PUCCH of the first cell. A first portion of the report 2604 (e.g., for the indexes RS 1 through RS N) may be similar to the beam report 2601, except that the first portion of the report 2604 is for the first cell (e.g., for RSs associated with the first cell). A second portion of the beam report 2604 may comprise one or more additional cell index fields for cell indexes of one or more cells (e.g., cells indicated by cell indexes “Cell 1” to “Cell K”) and one or more additional data fields respectively associated with the additional cell index fields. Each of the one or more additional cell indexes may be associated with a serving second cell (e.g., other than the first cell). The serving cells may be, for example, SCells. If there is no beam failure or a failure of a BFR procedure for a second cell indicated by a cell index in one of the cell index fields, a wireless device may leave empty the additional data field associated with that cell index field, or may populate that additional data field with a value (e.g., one of the reserved values from FIG. 25 ) indicative of no beam failure and/or of a successful BFR procedure. If there is a beam failure and/or a failure of a BFR procedure for a second cell indicated by a cell index in one of the cell index fields, a wireless device may populate the additional data field, associated with that cell index field, with a value (e.g., a different one of the reserved values from FIG. 25 (e.g., 1111111)) indicative of the unsuccessful BFR (and/or of the beam failure). A base station receiving the beam report 2604 may determine, for each of the one or more second cells associated with cell indexes in the cell index fields, whether a BFR procedure of that second cell was unsuccessful and/or whether a beam failure occurred in that second cell. That determination by the base station may be based on whether each of the additional data fields associated with the cell index fields is either (i) empty and/or populated a value indicative of no beam failure (or of successful BFR), or (ii) populated with a value indicative of an unsuccessful BFR (and/or of a beam failure). The base station may, based on determining an unsuccessful BFR procedure and/or a beam failure for one of the second cells, send a MAC CE to deactivate that second cell and/or may refrain from scheduling the wireless device on that second cell.

In the example of FIG. 26D, a wireless device may indicate that a random access procedure for a BFR procedure for a second cell, indicated in the beam report 2604 by the cell index “Cell 2,” was unsuccessful by populating the additional field, associated with the cell index field containing the cell index “Cell 2,” with a value (e.g., the reserved value 1111111 from FIG. 25 ) indicating an unsuccessful BFR procedure. A base station receiving that beam report 2604 may be informed of the failure of the BFR procedure for the second cell “Cell 2.” The base station may, based on the failed BFR procedure, send a MAC CE to deactivate, and/or may refrain from scheduling the wireless device on, the second cell “Cell 2.”

A wireless device may receive, for example, from a base station, one or more messages comprising one or more configuration parameters of a first cell (e.g., a PCell) and/or of a second cell (e.g., an SCell). The one or more configuration parameters may indicate at least one of one or more first RSs of the second cell; one or more second RSs of the second cell; and/or one or more beam BFRQ resources. The BFRQ resources may, for example, be on the first cell. The BFRQ resources may, for example, be on the second cell. The one or more configuration parameters may indicate an association between each of the one or more second RSs and each of the one or more BFRQ resources. The one or more first RSs may comprise one or more first CSI-RSs and/or one or more first SS blocks. The one or more second RSs may comprise one or more second CSI-RSs and/or one or more second SS blocks.

A wireless device may initiate a random access procedure for a beam failure recovery for the second cell based on, for example, reaching a number of beam failure instance indications for the second cell. The number of beam failure instance indications may be configured by a higher layer (e.g., an RRC layer). The beam failure instance indications may comprise, for example, an indication of a beam failure instance from a physical layer of the wireless device to a medium-access layer of the wireless device. The beam failure instance may comprise assessing the one or more first RSs with radio quality lower than a first threshold. The first threshold may, for example, be based on hypothetical BLER, on RSRP, on RSRQ, and/or on SINR. The wireless device may, based on, for example, the initiating the random access procedure, start a BFR timer (if configured).

The random access procedure may comprise, for example, selecting a selected RS in the one or more second RSs from the configuration parameters. The selected RS may be associated with a BFRQ resource. The BFRQ resource may be, for example, one of the one or more BRFQ resources from the configuration parameters. The BFRQ resource may comprise at least one preamble and at least one random access channel resource of a BWP. The random access procedure may further comprise sending (e.g., transmitting), by the wireless device, the at least one preamble via the at least one random access channel resource. The at least one random access channel resource may comprise one or more time resources and/or one or more frequency resources. The selected RS may, for example, be associated with one of the one or more second RSs with radio quality higher than a second threshold. The second threshold may be based on L1-RSRP, on RSRQ, on hypothetical BLER, and/or on SINR.

Based on sending (e.g., transmitting) the at least one preamble in a first slot, the wireless device may start, from a second slot, monitoring for a BFR response. The monitoring for the BFR response may comprise monitoring at least one PDCCH in one or more CORESETs for first DCI (e.g., a downlink assignment or an uplink grant) within a configured response window. The first DCI may be with CRC scrambled by a C-RNTI of the wireless device. The one or more CORESETs may, for example, be on the second cell. The one or more CORESETs may, for example, be on the first cell. The random access procedure for the BFR procedure may, for example, based on receiving the first DCI on the at least one PDCCH in the one or more CORESETs, within the configured response window, be successfully completed.

A BFR procedure may be unsuccessfully completed if, for example, a maximum number of transmissions of the at least one preamble via the BFRQ resource for the BFR procedure is reached without the BFR procedure being successfully completed. The maximum number of the transmissions (e.g., a maximum number of preamble transmissions) may be configured by a higher layer. A BFR procedure may be unsuccessfully completed if, for example, a BFR timer (if configured) expires before the BFR procedure is successfully completed (e.g., if the BFR timer expires before the wireless device receives, based on sending the at least one preamble, DCI within a configured response window).

A wireless device may send (e.g., transmit), based on a failure of a BFR procedure for an SCell, a beam report, The wireless device may send the beam report, for example, via an uplink control channel of the first cell. The beam report may comprise, for example, one or more fields indicating that the random access procedure for the beam failure recovery is unsuccessful. The beam report may be sent (e.g., transmitted) via a radio resource of periodic beam report resources of a PUCCH. The one or more fields may, for example, comprise one or more beam index fields and one or more associated measurement/data fields The one or more associated measurement/data fields may, for example, be used to indicate that the random access procedure for the beam failure recovery is unsuccessful by including, in one or more of the measurement/data fields (e.g., as described in connection with FIGS. 26A-26D), a value (e.g., a reserved value of FIG. 25 ) indicating unsuccessful beam failure recovery.

PUCCH beam reporting to indicate an unsuccessful BFR procedure and/or a beam failure, for example, as described in connection with FIGS. 26A-26C, may be used with CQI reporting. A wireless device may, for example, use a first CQI reporting of a second cell. The first CQI reporting may comprise one or more beam index fields and one or more measurement fields. One or more beam indexes indicated in the one or more beam index fields may be associated (e.g., QCLed) with one or more RSs of the second cell. Also or alternatively, one or more of the one or more beam index fields may not be associated with an RS and may be dedicated to and/or otherwise used for indicating an unsuccessful BFR procedure. Each of the one or more measurement fields may comprise a value that indicates a value or range of values (e.g., an L1-RSRP value or range of values) of one of the one or more beam indexes.

If the second cell has an unsuccessful BFR procedure, the wireless device may indicate the unsuccessful BFR procedure for the second cell by setting one or more of the one or more measurement fields in the CQI reporting to a value (e.g., reserved value (e.g., 0)) indicating unsuccessful BFR. A base station that receives the CQI reporting with one or more of the one or more measurement fields set to the value indicating unsuccessful BFR may be made aware of the failure of the BFR procedure of the second cell. The base station may, for example, based on the unsuccessful BFR, send a MAC CE to deactivate the second cell and/or may refrain from scheduling the wireless device on the second cell.

Using, for example, a report similar to that described in connection with FIG. 26D, a wireless device may send a second CQI reporting of a first cell (e.g., a PCell) to notify a base station of a failure of a BFR procedure for one or more serving second cells (e.g., SCells) other than the first cell. The second CQI reporting of the first cell may comprise, for the first cell, values (e.g., non-reserved values) indicating values or ranges of values for a characteristic. The second CQI reporting of the first cell may comprise an indication of a failure of random access procedure for a BFR of one or more of the second cells. The second CQI reporting of the first cell may comprise one or more additional cell index fields, comprising one or more additional cell indexes of the one or more second cells (e.g., the indexes “Cell 1” to “Cell K” shown in FIG. 26D), and one or more additional data fields. Each of the one or more additional cell indexes may be associated with one of the one or more second cells and with a value (or absence of a value) in one of the one or more additional data fields. If there is no beam failure or unsuccessful BFR procedure for one of the second cells, the associated additional data field may be empty or may comprise a value (e.g., a second reserved value) indicative of no beam failure and/or of no unsuccessful BFR procedure. If there is an unsuccessful BFR procedure (and/or beam failure) for one of the second cells, the associated additional data field may comprise a value (e.g., a first reserved value) indicative of beam failure and/or of an unsuccessful BFR procedure). A base station the receives the second CQI reporting of the first cell may determine, for each of the one or more second cells, whether a BFR procedure of that second cell was unsuccessful and/or whether a beam failure occurred in that second cell.

Other types of reporting may be used to report failure of a BFR procedure for an SCell. Periodic CSI reporting, for example, may be used to report an unsuccessful BFR procedure for an SCell. CSI reporting may be used, for example, similar to the use of beam reporting described in connection with FIGS. 26A-26B, to include an indicator (e.g., a reserved n-bit value from a set of n-bit values that includes indicators of measurements for one or more signal characteristics) of an unsuccessful BFR procedure for an SCell. The indicator of the unsuccessful BFR procedure may replace an indicator of a measurement, and/or may be included in addition to one or more indicators of the measurement.

An RLF report may, for example, comprise a serving cell index. Each of one or more serving cells of a wireless device may be configured with a serving cell index. The wireless device may, for example, if the wireless device has a failure of a BFR procedure for a serving cell, include the serving cell index of that serving cell in the RLF report. A base station, based on receiving the RLF report, may be made aware of the failure of the BFR procedure for the serving cell. The base station may, based on that failure of the BFR procedure, send a MAC CE to deactivate the serving cell and/or may refrain from scheduling the wireless device on the serving cell.

A base station may, for example, request an RLF report (e.g., periodically). An indication of a failure of a BFR procedure of a serving cell may be stored in an RLF report. The RLF report may contain a serving cell index of that serving cell. A wireless device information request procedure (e.g., an RRC UE information request procedure) may be reused to carry, to the network, that RLF report storing the indication of the failure of a BFR procedure.

One or more portions of one or more of the example reports described above, and/or one or more of the example procedures described above, may also or alternatively be used for other types of beam-related procedures. Reports (e.g., reports similar to those described in connection FIGS. 26B through 26D) may, for example, be used to report BFR procedures that have not yet completed and/or have not yet failed, to report BFR procedures that have successfully completed, and/or for other reporting.

A method may comprise receiving, by a wireless device, configuration parameters that indicate at least one reference signal (RS). The method may comprise initiating a beam failure recovery (BFR) procedure for a secondary cell. The method may comprise determining that the BFR procedure is unsuccessful. The method may comprise sending, via a physical uplink control channel (PUCCH), at least one message. The at least one message may comprise at least one field associated with the at least one RS. The at least one message may comprise at least one indicator of the unsuccessful BFR procedure. The at least one field may comprise at least one indicator of a value of a layer-1 reference signal received power (L1-RSRP) of the at least one RS. The at least one field may comprise the at least one indicator of the unsuccessful BFR procedure. The PUCCH may be associated with another secondary cell different from the secondary cell. The PUCCH may be associated with a primary cell. The method may comprise stopping, by the wireless device and based on the unsuccessful BFR procedure, monitoring of at least one downlink physical channel associated with the secondary cell. The method may comprise stopping, by the wireless device and based on the unsuccessful BFR procedure, uplink transmissions via the secondary cell. The configuration parameters may indicate a cell deactivation timer associated with the secondary cell. The stopping may comprise stopping, before expiration of the cell deactivation timer, the uplink transmissions via the secondary cell. The determining that the BFR procedure is unsuccessful may be based on at least one of: an expiration of a BFR timer associated with the secondary cell, or sending of a maximum quantity of uplink signals for the BFR procedure. The at least one RS may comprise a plurality of RSs, and the at least one field may comprise a plurality of fields associated with the plurality of RSs. The at least one RS may be associated with the secondary cell. The at least one RS may be associated with a primary cell. The at least one field may comprise an m-bit value selected from a plurality of m-bit values. A first portion of the plurality of m-bit values may be mapped to signal measurement values. A second portion of the plurality of m-bit values may optionally not be mapped to signal measurement values.

A method may comprise receiving, by a wireless device, configuration parameters that indicate at least one field associated with a measurement value associated with at least a first downlink signal. The method may comprise initiating a beam failure recovery (BFR) procedure for a secondary cell. The method may comprise determining that the BFR procedure is unsuccessful. The method may comprise sending, via a physical uplink control channel (PUCCH), at least one message comprising, in the at least one field, at least one indicator of the unsuccessful BFR procedure. The at least one message may comprise, for a second downlink signal, an indicator of a measurement value associated with the second downlink signal. The PUCCH may be associated with a primary cell. The method may comprise stopping, by the wireless device and based on the unsuccessful BFR procedure, uplink transmissions via the secondary cell.

A method may comprise initiating, by a wireless device, a beam failure recovery (BFR) procedure for a secondary cell. The method may comprise determining that the BFR procedure is unsuccessful. The method may comprise discontinuing, by the wireless device, based on the unsuccessful BFR procedure, and before expiration of a secondary cell deactivation timer associated with the secondary cell, at least one of: monitoring at least one downlink physical channel associated with the secondary cell, or uplink transmissions via the secondary cell. The method may comprise sending, via a physical uplink control channel (PUCCH), at least one message. The at least one message may comprise at least one indicator of the unsuccessful BFR procedure. The at least one message may comprise at least one indicator of a measurement value associated with at least one reference signal (RS). The method may comprise receiving, by the wireless device, one or more messages comprising configuration parameters that indicate the at least one RS. The at least one indicator of the measurement value may comprise at least one indicator of a value of a layer-1 reference signal received power (L1-RSRP) of the at least one RS.

A method may comprise receiving, by a wireless device, one or more messages comprising configuration parameters of a secondary cell, wherein the configuration parameters indicate one or more RSs of the secondary cell; initiating a BFR procedure for the secondary cell in response to reaching a number of beam failure instance indications for the secondary cell; determining that the BFR procedure is unsuccessfully completed; setting one or more fields, in a report for measurement values of the one or more RSs, to a reserved value based on the determining; and transmitting the report via a physical uplink control channel. Each of the one or more fields may correspond to a respective one of the one or more RSs. The report may comprise a cell index for each of the one or more fields. The physical uplink control channel may be a physical uplink control channel of the secondary cell. The physical uplink control channel may be a physical uplink control channel of a primary cell. The configuration parameters may further indicate a beam failure recovery timer. The determining that the BFR procedure is unsuccessfully completed may comprise expiring of the beam failure recovery timer. The configuration parameters further indicate a maximum number of uplink transmissions. The initiating the BFR procedure may comprise transmitting an uplink signal via an uplink resource. The method may comprise incrementing a transmission number based on the transmitting the uplink signal. The determining that the BFR procedure is unsuccessfully completed may comprise the transmission number reaching a maximum number of uplink transmissions. The method may comprise stopping one or more uplink transmissions via the secondary cell based on the determining that the BFR procedure is unsuccessfully completed. The method may comprise stopping monitoring at least one physical downlink control channel in a CORESET based on the determining that the BFR procedure is unsuccessfully completed. The CORESET may be configured for the secondary cell. The CORESET may be configured for a primary cell. The method may comprise transmitting an RLF report comprising the cell index. The method may comprise resuming the one or more uplink transmissions based on determining that a radio quality of at least one physical downlink control channel in the CORESET is higher than a threshold. The initiating the BFR procedure may comprise assessing one or more second RSs with radio quality lower than a second threshold. The configuration parameters may indicate the one or more second RSs for the secondary cell. The configuration parameters further indicate the second threshold. A method may comprise receiving, by a wireless device, one or more messages comprising one or more configuration parameters of a secondary cell; initiating a beam failure recovery procedure for the secondary cell in response to reaching a number of beam failure instance indications for the secondary cell; unsuccessfully completing the beam failure recovery procedure; and transmitting a beam report, via a physical uplink control channel, comprising a reserved value indicating that the beam failure recovery procedure has unsuccessfully completed.

FIG. 27 shows example elements of a computing device that may be used to implement any of the various devices described herein, including, e.g., the base station 120A and/or 120B, the wireless device 110 (e.g., 110A and/or 110B), or any other base station, wireless device, or computing device described herein. The computing device 2700 may include one or more processors 2701, which may execute instructions stored in the random access memory (RAM) 2703, the removable media 2704 (such as a Universal Serial Bus (USB) drive, compact disk (CD) or digital versatile disk (DVD), or floppy disk drive), or any other desired storage medium. Instructions may also be stored in an attached (or internal) hard drive 2705. The computing device 2700 may also include a security processor (not shown), which may execute instructions of one or more computer programs to monitor the processes executing on the processor 2701 and any process that requests access to any hardware and/or software components of the computing device 2700 (e.g., ROM 2702, RAM 2703, the removable media 2704, the hard drive 2705, the device controller 2707, a network interface 2709, a GPS 2711, a Bluetooth interface 2712, a WiFi interface 2713, etc.). The computing device 2700 may include one or more output devices, such as the display 2706 (e.g., a screen, a display device, a monitor, a television, etc.), and may include one or more output device controllers 2707, such as a video processor. There may also be one or more user input devices 2708, such as a remote control, keyboard, mouse, touch screen, microphone, etc. The computing device 2700 may also include one or more network interfaces, such as a network interface 2709, which may be a wired interface, a wireless interface, or a combination of the two. The network interface 2709 may provide an interface for the computing device 2700 to communicate with a network 2710 (e.g., a RAN, or any other network). The network interface 2709 may include a modem (e.g., a cable modem), and the external network 2710 may include communication links, an external network, an in-home network, a provider's wireless, coaxial, fiber, or hybrid fiber/coaxial distribution system (e.g., a DOCSIS network), or any other desired network. Additionally, the computing device 2700 may include a location-detecting device, such as a global positioning system (GPS) microprocessor 2711, which may be configured to receive and process global positioning signals and determine, with possible assistance from an external server and antenna, a geographic position of the computing device 2700.

The example in FIG. 27 may be a hardware configuration, although the components shown may be implemented as software as well. Modifications may be made to add, remove, combine, divide, etc. components of the computing device 2700 as desired. Additionally, the components may be implemented using basic computing devices and components, and the same components (e.g., processor 2701, ROM storage 2702, display 2706, etc.) may be used to implement any of the other computing devices and components described herein. For example, the various components described herein may be implemented using computing devices having components such as a processor executing computer-executable instructions stored on a computer-readable medium, as shown in FIG. 27 . Some or all of the entities described herein may be software based, and may co-exist in a common physical platform (e.g., a requesting entity may be a separate software process and program from a dependent entity, both of which may be executed as software on a common computing device).

The disclosed mechanisms herein may be performed if certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and/or the like. Example criteria may be based on, for example, wireless device and/or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like. If the one or more criteria are met, various examples may be used. It may be possible to implement examples that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wireless devices and/or base stations may support multiple technologies, and/or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and/or capability(ies). A base station may comprise multiple sectors. A base station communicating with a plurality of wireless devices may refer to base station communicating with a subset of the total wireless devices in a coverage area. Wireless devices referred to herein may correspond to a plurality of wireless devices of a particular LTE or 5G release with a given capability and in a given sector of a base station. A plurality of wireless devices may refer to a selected plurality of wireless devices, and/or a subset of total wireless devices in a coverage area. Such devices may operate, function, and/or perform based on or according to drawings and/or descriptions herein, and/or the like. There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, because those wireless devices and/or base stations perform based on older releases of LTE or 5G technology.

One or more features described herein may be implemented in a computer-usable data and/or computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other data processing device. The computer executable instructions may be stored on one or more computer readable media such as a hard disk, optical disk, removable storage media, solid state memory, RAM, etc. The functionality of the program modules may be combined or distributed as desired. The functionality may be implemented in whole or in part in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA), and the like. Particular data structures may be used to more effectively implement one or more features described herein, and such data structures are contemplated within the scope of computer executable instructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A module may be an isolatable element that performs a defined function and has a defined interface to other elements. The modules may be implemented in hardware, software in combination with hardware, firmware, wetware (i.e., hardware with a biological element) or a combination thereof, all of which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. Additionally or alternatively, it may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware. Examples of programmable hardware may comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors may be programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDs may be programmed using hardware description languages (HDL), such as VHSIC hardware description language (VHDL) or Verilog, which may configure connections between internal hardware modules with lesser functionality on a programmable device. The above-mentioned technologies may be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may comprise instructions executable by one or more processors configured to cause operations of multi-carrier communications described herein. An article of manufacture may comprise a non-transitory tangible computer readable machine-accessible medium having instructions encoded thereon for enabling programmable hardware to cause a device (e.g., a wireless device, wireless communicator, a wireless device, a base station, and the like) to allow operation of multi-carrier communications described herein. The device, or one or more devices such as in a system, may include one or more processors, memory, interfaces, and/or the like. Other examples may comprise communication networks comprising devices such as base stations, wireless devices or user equipment (wireless device), servers, switches, antennas, and/or the like. A network may comprise any wireless technology, including but not limited to, cellular, wireless, WiFi, 4G, 5G, any generation of 3GPP or other cellular standard or recommendation, wireless local area networks, wireless personal area networks, wireless ad hoc networks, wireless metropolitan area networks, wireless wide area networks, global area networks, space networks, and any other network using wireless communications. Any device (e.g., a wireless device, a base station, or any other device) or combination of devices may be used to perform any combination of one or more of steps described herein, including, for example, any complementary step or steps of one or more of the above steps.

Although examples are described above, features and/or steps of those examples may be combined, divided, omitted, rearranged, revised, and/or augmented in any desired manner. Various alterations, modifications, and improvements will readily occur to those skilled in the art. Such alterations, modifications, and improvements are intended to be part of this description, though not expressly stated herein, and are intended to be within the spirit and scope of the descriptions herein. Accordingly, the foregoing description is by way of example only, and is not limiting. 

The invention claimed is:
 1. A method comprising: determining, by a wireless device, that a beam failure recovery (BFR) procedure, for a beam failure associated with a cell, is unsuccessful; and sending, via a physical uplink control channel (PUCCH), at least one message comprising at least one measurement field associated with at least one reference signal (RS), wherein the at least one measurement field comprises a first value that indicates the unsuccessful BFR procedure associated with the cell.
 2. The method of claim 1, wherein the at least one measurement field further comprises at least one indicator of a value of an RS received power (RSRP) of the at least one RS.
 3. The method of claim 1, wherein the at least one message further comprises at least one field comprising a value indicating the at least one RS.
 4. The method of claim 1, wherein the PUCCH is associated with at least one of: a primary cell; or a secondary cell different from the cell.
 5. The method of claim 1, further comprising stopping, based on the unsuccessful BFR procedure, at least one of: uplink transmissions via the cell; or monitoring of at least one downlink channel associated with the cell.
 6. The method of claim 1, further comprising: receiving at least one configuration parameter indicating a cell deactivation timer associated with the cell; and stopping, before expiration of the cell deactivation timer and based on the unsuccessful BFR procedure, at least one of: uplink transmissions via the cell; or monitoring of at least one downlink channel associated with the cell.
 7. The method of claim 1, wherein the determining that the BFR procedure is unsuccessful is based on at least one of: an expiration of a BFR timer associated with the cell; or sending of a maximum quantity of uplink signals for the BFR procedure.
 8. The method of claim 1, wherein the at least one RS comprises a plurality of RSs, and wherein at least one field, of the at least one message, comprises a plurality of fields associated with the plurality of RSs.
 9. The method of claim 1, wherein the at least one RS comprises at least one of: an RS of a primary cell; an RS of a secondary cell; or an RS of the cell.
 10. The method of claim 1, further comprising: receiving at least one configuration parameter that indicates the at least one RS; and determining a beam failure associated with the cell.
 11. The method of claim 1, wherein the first value corresponds to a reserved value of a plurality of layer-1 RS received power (L1-RSRP) values, and wherein a second value, different from the reserved value, for the at least one measurement field of the at least one message is configured to indicate a measured L1-RSRP.
 12. The method of claim 1, further comprising measuring the at least one RS for measurement reporting, wherein the at least one measurement field is configured to indicate a measured characteristic of the at least one RS.
 13. The method of claim 1, wherein the first value corresponds to a reserved value associated with an RS received power, and wherein the at least one message further comprises a second value, different from the reserved value, for indicating an RS received power associated with another cell different from the cell.
 14. A wireless device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to: determine that a beam failure recovery (BFR) procedure, for a beam failure associated with a cell, is unsuccessful; and send, via a physical uplink control channel (PUCCH), at least one message comprising at least one measurement field associated with at least one reference signal (RS), wherein the at least one measurement field comprises a first value that indicates the unsuccessful BFR procedure associated with the cell.
 15. The wireless device of claim 14, wherein the at least one measurement field further comprises at least one indicator of a value of an RS received power (RSRP) of the at least one RS.
 16. The wireless device of claim 14, wherein the at least one message further comprises at least one field comprising a value indicating the at least one RS.
 17. The wireless device of claim 14, wherein the PUCCH is associated with at least one of: a primary cell; or a secondary cell different from the cell.
 18. The wireless device of claim 14, wherein the instructions, when executed by the one or more processors, cause the wireless device to stop, based on the unsuccessful BFR procedure, at least one of: uplink transmissions via the cell; or monitoring of least one downlink channel associated with the cell.
 19. The wireless device of claim 14, wherein the instructions, when executed by the one or more processors, cause the wireless device to: receive at least one configuration parameter indicating a cell deactivation timer associated with the cell; and stop, before expiration of the cell deactivation timer and based on the unsuccessful BFR procedure, at least one of: uplink transmissions via the cell; or monitoring of at least one downlink channel associated with the cell.
 20. The wireless device of claim 14, wherein the instructions, when executed by the one or more processors, cause the wireless device to determine that the BFR procedure is unsuccessful based on at least one of: an expiration of a BFR timer associated with the cell; or sending of a maximum quantity of uplink signals for the BFR procedure.
 21. The wireless device of claim 14, wherein the at least one RS comprises a plurality of RSs, and wherein at least one field, of the at least one message, comprises a plurality of fields associated with the plurality of RSs.
 22. The wireless device of claim 14, wherein the at least one RS comprises at least one of: an RS of a primary cell; an RS of a secondary cell; or an RS of the cell.
 23. The wireless device of claim 14, wherein the instructions, when executed by the one or more processors, cause the wireless device to: receive at least one configuration parameter that indicates the at least one RS; and determine a beam failure associated with the cell.
 24. The wireless device of claim 14, wherein the first value corresponds to a reserved value of a plurality of layer-1 RS received power (L1-RSRP) values, and wherein a second value, different from the reserved value, for the at least one measurement field of the at least one message is configured to indicate a measured L1-RSRP.
 25. The wireless device of claim 14, wherein the instructions, when executed by the one or more processors, cause the wireless device to measure the at least one RS for measurement reporting, and wherein the at least one measurement field is configured to indicate a measured characteristic of the at least one RS.
 26. The wireless device of claim 14, wherein the first value corresponds to a reserved value associated with an RS received power, and wherein the at least one message further comprises a second value, different from the reserved value, for indicating an RS received power associated with another cell different from the cell.
 27. A non-transitory computer-readable medium storing instructions that, when executed, configure a wireless device to: determine that a beam failure recovery (BFR) procedure, for a beam failure associated with a cell, is unsuccessful; and send, via a physical uplink control channel (PUCCH), at least one message comprising at least one measurement field associated with at least one reference signal (RS), wherein the at least one measurement field comprises a first value that indicates the unsuccessful BFR procedure associated with the cell.
 28. The non-transitory computer-readable medium of claim 27, wherein the at least one measurement field further comprises at least one indicator of a value of an RS received power (RSRP) of the at least one RS.
 29. The non-transitory computer-readable medium of claim 27, wherein the at least one message further comprises at least one field comprising a value indicating the at least one RS.
 30. The non-transitory computer-readable medium of claim 27, wherein the PUCCH is associated with at least one of: a primary cell; or a secondary cell different from the cell.
 31. The non-transitory computer-readable medium of claim 27, wherein the instructions, when executed, further configure the wireless device to stop, based on the unsuccessful BFR procedure, at least one of: uplink transmissions via the cell; or monitoring of least one downlink channel associated with the cell.
 32. The non-transitory computer-readable medium of claim 27, wherein the instructions, when executed, further configure the wireless device to: receive at least one configuration parameter indicating a cell deactivation timer associated with the cell; and stop, before expiration of the cell deactivation timer and based on the unsuccessful BFR procedure, at least one of: uplink transmissions via the cell; or monitoring of at least one downlink channel associated with the cell.
 33. The non-transitory computer-readable medium of claim 27, wherein the instructions, when executed, further configure the wireless device to determine that the BFR procedure is unsuccessful based on at least one of: an expiration of a BFR timer associated with the cell; or sending of a maximum quantity of uplink signals for the BFR procedure.
 34. The non-transitory computer-readable medium of claim 27, wherein the at least one RS comprises a plurality of RSs, and wherein at least one field, of the at least one message, comprises a plurality of fields associated with the plurality of RSs.
 35. The non-transitory computer-readable medium of claim 27, wherein the at least one RS comprises at least one of: an RS of a primary cell; an RS of a secondary cell; or an RS of the cell.
 36. The non-transitory computer-readable medium of claim 27, wherein the instructions, when executed, further configure the wireless device to: receive at least one configuration parameter that indicates the at least one RS; and determine a beam failure associated with the cell.
 37. The non-transitory computer-readable medium of claim 27, wherein the first value corresponds to a reserved value of a plurality of layer-1 RS received power (L1-RSRP) values, and wherein a second value, different from the reserved value, for the at least one measurement field of the at least one message is configured to indicate a measured L1-RSRP.
 38. The non-transitory computer-readable medium of claim 27, wherein the instructions, when executed, further configure the wireless device to measure the at least one RS for measurement reporting, and wherein the at least one measurement field is configured to indicate a measured characteristic of the at least one RS.
 39. The non-transitory computer-readable medium of claim 27, wherein the first value corresponds to a reserved value associated with an RS received power, and wherein the at least one message further comprises a second value, different from the reserved value, for indicating an RS received power associated with another cell different from the cell. 